You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This allows derives to be used in functions (see workaround from rust-lang/rust#51952). The problem is that extern crate seems to be hard or impossible to use in a function scope, so it will most likely be a breaking change.
The text was updated successfully, but these errors were encountered:
113: Import everything from the parent scope in derives r=Ogeon a=Ogeon
This removes the warnings without breaking anything that wasn't broken before. Turns out that `extern crate` in a function scope has some strange behaviors, so I'm not going to do the function change just yet. I will change #111 not be about the hygiene warning, but just un-breaking cases where `#[derive(...)]` is already broken.
Co-authored-by: Erik Hedvall <erikwhedvall@gmail.com>
It may be possible to use https://crates.io/crates/find-crate to find a way around the problem. I think it will allow us to refer to the crate via a global path (::#name::thing, provided it works and doesn't print warnings in both Rust editions). Then it's up to the user to write extern crate where/if necessary.
This allows derives to be used in functions (see workaround from rust-lang/rust#51952). The problem is that
extern crate
seems to be hard or impossible to use in a function scope, so it will most likely be a breaking change.The text was updated successfully, but these errors were encountered: