Add Windows-specific note about stdout initialization at compile-time

[KorryKatti]

Added a note about Windows behavior when using const stdout = std.io.getStdOut().writer() outside functions. On Windows, this expression is evaluated at compile-time, which may cause issues. The solution is to place it inside a function to avoid compile-time evaluation.

[pedropark99]

Uhmm, interesting, do you know if this issue is documented somewhere? Maybe in a GitHub issue? Or, in a specific section of the official Zig docs?

[KorryKatti]

Uhmm, interesting, do you know if this issue is documented somewhere? Maybe in a GitHub issue? Or, in a specific section of the official Zig docs?

my only knowledge of zig is from your book really 😅but i noticed this problem while coding and confirmed with 2-3 more people who i know.

[KorryKatti]

when the stdout is outside the pub fn function:

error:

code:

when stdout is inside the function :

output :

code:

[KorryKatti]

it is probably a windows only problem

[pedropark99]

Found two issues that document this specific requirement on Windows:

• (Windows only) Putting "std.io.getStdOut().writer()" variable globally leads to compile error ziglang/zig#19864
• Compilation fails while trying to getStdInHandle only when target is set to x86_64-windows ziglang/zig#17186