0.14.0 is one month out

I very new to zig and found this one too.

What about marking with compileLog when function is deprecated and then when it is decided to remove it, mark it with compileError?

on the next stable release remove then all compileError

it takes more time to really remove the function but for people that go from one stable release to another they will get the message.

compileLog still generates a compile error. From the docs:

To prevent accidentally leaving compile log statements in a codebase, a compilation error is added to the build, pointing to the compile log statement. This error prevents code from being generated, but does not otherwise interfere with analysis.

1 Like