-
Notifications
You must be signed in to change notification settings - Fork 59
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
Unify with in-tree compiletest-rs #238
Comments
I sorta-kinda tried to address this in #201, but never got around to finishing it. My impression was that rustc had some exotic requirements for its internal compiletest that were hard to generalise for this package. I don't expect I'll get back to working on that PR anytime soon, and it's probably diverged too far from upstream by now to be of any real use, but it is there, if anyone wants to take a look. |
Yeah I'm wondering if we can keep those requirements but perhaps behind a flag. |
I really don't want us to have to maintain this as a fork 😄 |
Instead of doing a merge, we could potentially try a "fresh start" where we first try moving compiletest out of tree, and if that works, release it as a breaking version bump to this crate, making sure major users (clippy, syn) have everything they need to upgrade. |
Yeah, we should try to minimize the maintenance burden as much as possible. |
That may not be a bad idea. At least, it's worth a shot :-) |
Filed rustc side of this issue in rust-lang/rust#82946 |
I'd like for us to eventually have a world where rustc simply depends on compiletest-rs, and compiletest-rs lives in rust-lang
Blockers:
test
crate Remove dependency ontest
crate #237The text was updated successfully, but these errors were encountered: