Drake Tetreault

I added a warning about not polling futures from an interrupt routine. However, are interrupts actually a problem so long as they occur on the same core? I get that...

I have attempted to add wasm32-unknown-unknown target support to version `0.11.0` of this crate which was just published. The `rt` feature will be used instead of the `rt-multi-thread` feature on...

I have just pushed support for a new `env_lit!` macro to master which allows arbitrary literals/expressions to be used. This includes array literals, struct literals, etc. Example: ```sh export MY_ENV_VAR="[1,...

I've published `0.1.4` to crates.io which contains the new `env_lit!` macro which allows for arrays, struct literals, etc.

The `tracked` feature of this crate is intended to solve this problem. Enabling it requires using an unstable Rust compiler due to the dependency on https://github.com/rust-lang/rust/issues/99515.

Going to close this as the unstable `proc_macro::tracked_env::var` is the best way to do this that I'm aware of, and the `tracked` feature of this crate allows users to opt-in...

That's interesting, I'll reopen this to track adding that workaround to the code.

I implemented your suggested approach and tested that it does allow tracking to work even when using a stable compiler. I've published version `0.1.5` with the improvement. Thanks for the...