Add Windows-specific note about stdout initialization at compile-time #94
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
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. |
when the stdout is outside the pub fn function:error:code:when stdout is inside the function :output :code: |
|
it is probably a windows only problem |
|
Found two issues that document this specific requirement on Windows: |
pedropark99
approved these changes
Nov 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.