I think this is an easy issue I submitted. Any suggestion?
cargo nextest-gen-dev
will run tests using the dev backend. If you want to use the LLVM backend you can use cargo nextest-gen-llvm
I wanted to test the dev backend, which fail withcargo nextest-gen-dev
for test nested_switch
with a pointer error, but cargo nextest run --locked --release --package test_gen --no-default-features --features gen-dev --no-fail-fast
does not fail and I thought I broke something until I ran the longer command.
Sorry for the double chating with github and zulip, I'll stick to Github.
Zulip is probably better tbh. I need to head off now sorry. I can respond tomorrow, but Im also probably not the best person to help you with this issue.
Last updated: Jul 06 2025 at 12:14 UTC