-
Notifications
You must be signed in to change notification settings - Fork 242
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
Incoming nightly breakage #189
Comments
Thanks for the heads up! This repository is basically archived at this point, and the upstream crate hasn't been updated in a while, so I probably won't go through and fix this, but this should be helpful to anyone who does want to pick up the code. So I'll leave it open :) |
So the project is not under active development anymore? |
No, I haven't worked on this since I graduated back in November 2020, and I don't think anyone's currently continuing the research in my lab at MIT either. This repository was, and still is, a research prototype :) |
Hi @jonhoo based on the breaking changes coming in can you help state clearly which version of nightly one needs to run this project smoothly. Thanks a lot. |
Ah, that's a good question. I last worked on this end of November 2020, so a nightly from around there is likely to work. I don't have an exact date though. |
While your crate does nothing wrong per se, the incoming breakage may be somewhat annoying, and you can get ahead of the breakage.
The PR that will break this crate: rust-lang/rust#94081
The breakage: https://crater-reports.s3.amazonaws.com/pr-94081/try%23e251c42c969d6f8dbaae00e1028489c3a29f8789/reg/noria-common-0.6.0/log.txt
The fix is to move
noria/noria/src/controller.rs
Line 358 in 465184e
noria/noria/src/controller.rs
Line 179 in 465184e
impl Trait
usage in the return type.On a positive note: rust-lang/rust#65442 is now very much on my radar, with the PR that breaks your code this becomes actually fixable without a complex hack!
The text was updated successfully, but these errors were encountered: