I have a #rust crate which is reliably building in the stable channel releases of the last 4 months and has been reliably not building in the nightly channel release of the last 4 months. I am not enabling any unstable features.
What could be the problem?
I only arbitrarily stopped at 4 months ago to go to bed. I did not check yet how far back I can see this issue. But my understanding of the rustc release model tells me this shouldn’t happen…
=> More informations about this toot | More toots from matzipan@hachyderm.io
@matzipan the error message seems to come from inside the macro expansion for #[derive(lox_derive::KvnDeserialize)]
I've had vaguely similar problems in proc macros before - it's usually been due to the syn / proc-macro2 crates detecting the current Rust version in their build.rs and generating different code on nightly.
=> More informations about this toot | More toots from decathorpe@mastodon.social
@decathorpe oh that’s interesting. I will expand today
=> More informations about this toot | More toots from matzipan@hachyderm.io
text/geminiThis content has been proxied by September (ba2dc).