-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
core::compiler: remove Executor trait #11428
Conversation
Failed to set assignee to
|
Signed-off-by: Nick Cameron <nrc@ncameron.org>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello Nick! I am happy that RLS retired gloriously and reducing code complexity sounds great to me! However, I am not sure i there are projects depend on Executor
trait heavily. From my naive search result on GitHub, there are at least three projects depending on it:
- https://github.com/defuse/siderophile/blob/955a714468439330ae7627cadb86b1851acfc270/src/deps.rs#L386
- https://github.com/not-fl3/cargo-quad-apk/blob/672249200d1054b8a609cd1220d869f652e251ee/src/ops/build/compile.rs#L110
- https://github.com/lu-zero/cargo-c/blob/76a66cd72eb4271501557eebea7060821e63b702/src/build.rs#L797
I didn't look into them. Perhaps we can provide them alternatives (if those tools are still in maintenance).
The first project hasn't been touched for four years, but the other two seem to be maintained. I guess we need to keep supporting this API unless we can provide an alternative or there is really good reason not to. |
☔ The latest upstream changes (presumably #11430) made this pull request unmergeable. Please resolve the merge conflicts. |
Now rust 1.50 is supported
Just posted comments for those projects. I'll take over this PR if either they agree to this or no reply for a while. |
Okay. Got a reply from the author of |
What does this PR try to resolve?
This PR remove the Executor trait and thus simplifies some code. I added this trait for the RLS and it was never advertised as a publicly available API. The RLS is dead now and I think this API is not the best way to achieve its goals, therefore I think it should be removed.
How should we test and review this PR?
Change is trivial refactoring, so existing tests should be fine. Eyeball review should be fine.
Additional information
r? @arlosi