Owen Avery
Owen Avery
It looks like [```target..rustflags```](https://doc.rust-lang.org/cargo/reference/config.html#targettriplerustflags) and [```link-args```](https://doc.rust-lang.org/rustc/codegen-options/index.html#link-args) could be used to pass arguments to the linker. We could split ```$(LINKER)``` into an executable and argument list if need be.
I managed to reduce it to ```rust #![feature(lang_items)] #[lang = "sized"] trait Sized {} pub struct A(T); pub trait B { type C; } // ------ // swap these two...
git bisect blames ```12131c106fdffe25c40fa4a309d8ead03b99a685```
https://rustc-dev-guide.rust-lang.org/macro-expansion.html It looks like import resolution should be attempted multiple times, until no more resolution can be done.
Note that, until name resolution 2.0 improves sufficiently, a decent fraction of new tests after this is merged (?) will have to be entered into the ```exclude``` file.
Thoughts on merging this? Should I make some tweaks?
Ah, I didn't realize nr2.0 was so close to completion. The idea was that every compile test for non-nr2.0 would automagically run with nr2.0 as well, except for those in...
Where is the development on nr2.0 taking place? I think I might be a bit out of the loop
When I try to force-enable nr2.0 on `allow-use-before-items-being-used-continued` (by replacing `flag_name_resolution_2_0` references with `1`) I get a bunch of test errors. Are you sure there's only one non-working test?
Yep, looks like it needs some tweaks after some tests were moved around. Will need to be adjusted to handle sub directories properly.