Jeremiah Senkpiel
Jeremiah Senkpiel
If that future is a large set of async functions you may be able to break it up manually using a pinned box for some memory indirection, which should help...
Needs a rebase.
Hi, my employer uses self hosted runners on AWS (for security reasons). We'd like to do actions caching for Rust language intermediary build artifacts. It would be nice to not...
All the checkboxes in the original issue post here have been checked off - can an updated checklist be made if this is not ready to be stabilized?
>I'm not sure which original issue you are referring to. Work is still actively being performed on this, mainly the amazing effort from @arlosi: > > ... pr links ......
Stabilizing this without making `cargo:token` a default option (which would have respected the world as it functioned before 1.74) has broken all of our CI: https://rust-lang.zulipchat.com/#narrow/stream/246057-t-cargo/topic/Cargo.201.2E74.20broke.20all.20our.20CI.20due.20to.20credentials-process
Ok so, this is currently in my `env.nu`, and seems to at least not have nushell 0.71 errors ```nu # FNM # load env variables fnm env --json | from...
Full fnm script for nu 0.73 ```nu # FNM # load env variables fnm env --json | from json | load-env # add dynamic fnm path let-env PATH = ($env.PATH...
@aldanor IIRC this is due to the absence of async closures in Rust.
So I've been thinking about this for a couple weeks, and I have felt that non-exhaustive implementations did not sit well with me for some reason(s) I couldn't quite put...