When debug=false it says
brian@DESKTOP-UCV672I:~/dbgtest$ cargo build --release
Finished release [optimized] target(s) in 0.06s
When debug=0 it says
Finished release [optimized + debuginfo] target(s) in 0.06s
My understanding is that "0" and "false" both mean "no debuginfo", but cargo claims otherwise. Cargo also passes the -Cdebuginfo=0 flag to rustc when debug=0 and does not when debug=false. For consistency, and as a matter of defensiveness it seems like it should pass the flag anyway.