Re:The C++ standard for the F-35 Fighter Jet [video]
by dnautics on Sunday December 07, 2025 @07:21PM
(#46186887)
there was a recent interview where andrew suggested if i understood correctly: the future path of zig is to make all compilations (successful or not) produce an executable. if theres something egregious like a syntax or type error, the produced artifact just prints the error and returns nonzero. for a "unused parameter", the compiler produces the artifact you expect, but returns nonzero (so it gets caught by CI for example.
[ Parent
| on HN ]
Re:The C++ standard for the F-35 Fighter Jet [video]
by sumalamana on Sunday December 07, 2025 @07:27PM
(#46186929)
Why would the compiler do that, instead of just printing the error at compile-time and exiting with a non-zero value? What is the benefit?
Re:The C++ standard for the F-35 Fighter Jet [video]
by j16sdiz on Sunday December 07, 2025 @11:40PM
(#46188398)
It is more a debug/development feature. You can try out some idea without fixing the whole code base.
Re:The C++ standard for the F-35 Fighter Jet [video]
by dnautics on Monday December 08, 2025 @10:45AM
(#46193620)
if you have a syntax error in file A, and file B is just peachy keen, you can keep compiling file B instead of stopping the world. Then the next time you compile, you have already cached the result of file B compilation.