Is there a compiler flag to tell me about dead code? | Zig Programming Language | Page 1

hexed bay Sep 16, 2022, 10:11 AM

#

Particularly in zig build test. I would like some way to tell what functions are not compiled and therefore untested.

crystal flicker Sep 16, 2022, 10:18 AM

#

this will eventually be a compile error iirc

#

idk about currently tho

left scarab Sep 16, 2022, 11:41 AM

#

There's no real way to do that

#

Because conditional compilation means you might have functions that are only used on certain platforms

hexed bay Sep 16, 2022, 12:29 PM

#

That's not unsolvable though, right? It would be possible to see that the reason the dead code wasn't generated was that you weren't compiling for the platform it was used on and omit it from the report since that info is all known at compile time. I think there's a big conceptual difference between dead code because it's not used anywhere and dead code because it's not used here

tiny loom Sep 16, 2022, 12:49 PM

#

This will be a class of error, according to this accepted proposal: https://github.com/ziglang/zig/issues/335

GitHub

compile errors for unused things · Issue #335 · ziglang/zig

compile error for unused non-pub global variable compile error for unused local variable compile error for unused non-pub function decl compile error for unreachable code (astgen only) even unused ...

#

atm, only applying to unused private functions

#

it seems that it was also going to apply to unused pub functions that were not reachable from outside the package in a library, but that was crossed out, probably because of some technical limitation

#Is there a compiler flag to tell me about dead code?