No/missing debug information for const variables.

[Srekel]

Zig Version

0.13.0

Steps to Reproduce and Observed Behavior

I'm on Windows 11 Home.

Please see attached image - this is using the latest (as of today) VS Code, All extensions up to date and using corresponding ZLS version as far as I can tell.

Expected Behavior

In this case I expected helloconst to show up under Locals or at least that I can inspect it under Watch. In this case it is of course a trivial value but as we all know consts can be significantly more complex.

I also expected lolconst to resolve OK under Watch.

Even when consts are just a little bit complex, like in the case below, it can be quite useful when debuugging to immediately be able to check that, say, max_patch_int is the value you expect it to be.

const lod_0_patch_size = config.patch_size;
const max_world_size = 4 * 1024; // 512 * 1024; // 500 km
const max_patch = max_world_size / lod_0_patch_size; // 8k patches
const max_patch_int_bits = 16; // 2**13 = 8k
const max_patch_int = std.meta.Int(.unsigned, max_patch_int_bits);

Related: #20258.
Related: #15095

[ni-vzavalishin]

In your example helloconst doesn't seem to be referenced anywhere. I'd accept the fact that unreferenced entities are not really compiled in or present in anyway. However I also regularly had debug visibility issues with referenced constants, which is a totally different story IMHO. Not sure if there's an existing bug for that.

[mlugg]

Indeed, unreferenced values won't show up in debuggers, because of Zig's lazy analysis, so that explains helloconst. However, lol and lolconst definitely ought to be shown.

[Srekel]

Ah, fair! Here is what it looks like when it's referenced. It still doesn't show up in Locals, which I would assume it would, but it does show up in watch.

(Globals not showing up in Locals may of course be a VS Code issue or design choice on their part, but if Zig has the choice of listing variables that are on level higher that would at least be my preference. )