Manish Goregaokar

Good to know, thanks. On Fri, Apr 12, 2019, 9:32 AM Nicolas Silva wrote: > I currently don't have the bandwidth to delve into the gecko side. > > —...

I'm not really sure! I think it's possible, but it might be annoying

We should do this for dataful enums, C-like enums should still just fetch a number from the cursor position.

No strong thoughts, we can allow multiple methods for overriding it perhaps.

From a maintenance pov i strongly agree that this should be a separate trait. I'm also wary but I'm happy to defer to fitzgen's judgement on this and agree with...

> I realize that there's a workaround: use conditional compilation to turn on std in the crate when fuzzing, and only derive Arbitrary in that context. The value I see...

@jyn514 I suspect something with cargo-make that invokes a bash script that calls `cargo +version build` would be an MCVE, ideally one using some unstable stuff

Another error that we're seeing is: ``` error: "/home/runner/.rustup/toolchains/1.61-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/Cargo.lock" does not exist, unable to build with the standard library, try: rustup component add rust-src --toolchain nightly-2022-04-05-x86_64-unknown-linux-gnu ``` Which I _think_...

> ``` > error: "/home/runner/.rustup/toolchains/1.61-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/Cargo.lock" does not exist, unable to build with the standard library, try: > rustup component add rust-src --toolchain nightly-2022-04-05-x86_64-unknown-linux-gnu > ``` Okay, looking at this further...

> If you are doing cross-builds from within invocations of `cargo` are you perhaps not being sure to clean your environment of things like `RUSTC` `RUSTDOC` `RUSTFLAGS` or other environment...