Eric Holk
> Hi. If I want to verify the behavior of this patch. What environment should I prepare? Specifically, can you provide some official doc about this change? Thanks! I'm on...
Sure, here's the output from `cargo test -- package::reserved_windows_name --nocapture` on `master`: ``` Finished test [unoptimized + debuginfo] target(s) in 0.27s Running unittests src/cargo/lib.rs (target\debug\deps\cargo-9040197b200da57a.exe) running 0 tests test result:...
That seems reasonable. If I remember right, the code for publishing packages tries to prevent you from publishing packages that couldn't be unpacked on all OSes supported by Cargo, so...
I decided to close this PR in favor of #10461 which cleanly does what was decided in the discussion here.
Reopening this since there's disagreement about whether we want this change or the one in #10461. We only need one of these to land though.
> In that spirit, and in the spirit of not providing this as a public API of Cargo, could you move this function into the test code rather than the...
I thought about using `&'static` instead of `*` for the EFI stuff, but I'm not sure I have a good reason to prefer one way or the other. The code...
Nice!
It seems like this would be possible with a build.rs script. Using Cargo would be far nicer than my hacked together Makefiles!
The `record-case` macro might work for a lot of cases. It could possibly even be integrated into the `match` macro.