Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor(core)!: remove EitherFuture2 #3340

Merged
merged 24 commits into from
Jan 18, 2023
Merged

Conversation

thomaseizinger
Copy link
Contributor

Description

We can completely replace EitherFuture2 with EitherFuture. EitherFuture itself cannot be removed for now because the Future implementation on future::Either forces both Futures to evaluate to the same type.

Notes

Links to any relevant issues

Open Questions

Change checklist

  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • A changelog entry has been made in the appropriate crates

core/CHANGELOG.md Outdated Show resolved Hide resolved
core/CHANGELOG.md Outdated Show resolved Hide resolved
Copy link
Member

@jxs jxs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM thanks for this Thomas!

Base automatically changed from 2650-remove-either-upgrade to master January 18, 2023 02:35
@mergify
Copy link
Contributor

mergify bot commented Jan 18, 2023

This pull request has merge conflicts. Could you please resolve them @thomaseizinger? 🙏

@mergify mergify bot merged commit 73cbbe2 into master Jan 18, 2023
@mergify mergify bot deleted the 2650-remove-either-future2 branch January 18, 2023 10:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants