jyn
jyn
hmm. probably this should only happen for the editor mode, not searches or xdg-open. one sec.
https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/live.20previews.20for.20rustc-dev-guide.3F/with/520974503
for posterity, the full error was ``` Compiling test-crate v0.1.0 (/Users/runner/work/cmake-rs/cmake-rs/test-crate) error: linker stderr: ld: search path '/Users/runner/work/cmake-rs/cmake-rs/test-crate/target/debug/build/libz-sys-ae8c893dbe111c55/out/lib64' not found ld: object file (/Users/runner/work/cmake-rs/cmake-rs/test-crate/target/debug/deps/liblibz_sys-297f35bb33641431.rlib[31](zutil.c.o)) was built for newer 'macOS' version...
note that i do *not* plan to silence the "search path" not found error, so that will eventually come back unless someone makes a convincing case why it shouldn't.
ok, I think this idea cannot work. ``` impl, C: std::iter::FromIterator + std::iter::IntoIterator> Arbitrary) -> Result { u.arbitrary_iter().collect() } } ``` ``` 1 error[E0119]: conflicting implementations of trait `Arbitrary Arbitrary...
i ended up not needing this (turns out smallvec already supports `arbitrary` and i needed custom logic for my dashmap struct anyway) but i don't mind keeping the issue open...
"can't find crate for..." proc-macro crates when the crate is clearly present and is passed to rustc
nora ran cargo bisect-rustc and found this: ``` Regression in nightly-2024-07-13 ... looking for regression commit between 2024-07-12 and 2024-07-13 fetching (via remote github) commits from max(5315cbe15b79533f380bbb6685aa5480d5ff4ef5, 2024-07-10) to c6727fc9b5c64cefa7263486497ee95e529bd0f8...
"can't find crate for..." proc-macro crates when the crate is clearly present and is passed to rustc
this bit here: https://github.com/rust-lang/rust/blob/c9f690a1e3d42f80788e9e4f2aa25547b1d8df58/compiler/rustc_metadata/src/creader.rs#L516-L535 is rejecting a previously loaded crate, but i'm not sure why
"can't find crate for..." proc-macro crates when the crate is clearly present and is passed to rustc
there is additional logging in the non-working case that i didn't post at first; here it is: ``` INFO rustc_metadata::creader resolving crate `poem_derive` INFO rustc_metadata::creader falling back to a load...
"can't find crate for..." proc-macro crates when the crate is clearly present and is passed to rustc
i think there is a secondary issue which is that this should have reported [E0519 ](https://doc.rust-lang.org/error_codes/E0519.html) instead of "crate not found". the last code to touch that was https://github.com/rust-lang/rust/pull/111461 but...