stabilizer VS cargo-show-asm

Yes, just because it's from a team connected with the old Stabilizer tool, it doesn't mean it shares the insights and benefits of that kind of testing. At least, that's my understanding of coz, based on my knowledge of https://github.com/ccurtsinger/stabilizer

Nope, he is thinking of that team's previous work, stabilizer. See this talk for more information on both. It is an excellent talk.

Other researchers have tried building tools to address this issue : stabilizer. Unfortunately, stabilizer is now outdated as it hasn't been upgraded from it's LLVM 3.1 foundation. See the project here : https://github.com/ccurtsinger/stabilizer

I see a lot a value in stabilizer.

Any thoughts on using stabilizer in the future?: https://github.com/ccurtsinger/stabilizer

https://github.com/pacak/cargo-show-asm/tree/semantic - how all of this is used

Go to https://github.com/pacak/cargo-show-asm/issues/new

https://github.com/pacak/cargo-show-asm/pull/88 - will release in a day or two unless there's some more urgent fixes.

In this case, I used cargo-show-wasm

Executing cargo-show-asm on the before and after doesn't show large difference in total lines emitted (1061 vs 1102):

If you are using bpaf in a situation where you don't really care about the compilation time (or you do but already have proc macros) you just put the main options struct on top and describe the rest in any style: https://github.com/pacak/cargo-show-asm/blob/master/src/opts.rs