-
Notifications
You must be signed in to change notification settings - Fork 486
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unclear why garbage values are what they are in 38 #43
Comments
You're absolutely right. I need to add a note that clarifies this. Thank you! |
@AtomToast Clarification added at the end of the exercise. Thanks again for pointing this out! |
I came here to ask the same question because I didn't read to the end of exercise... Thanks for adding this clarification and nice choice of placeholder bytes on the zig team side 😏 |
Hmm...I wonder if I need to draw attention to the end-of-exercise notes? Glad you found it! |
Hey, thanks a lot for the ziglings! They really are helping me get started.
In zigling number 38 you mention
For me it was unclear why exactly the garbage values are what they are. (2863311530, 170 and 2863311530).
So I went out and looked a bit to discover that they are basically just filled with 0xAAAAAA...
Then someone in the zig matrix room sent me the link to the zig documentation, clarifying why exactly this was the case
According to your contribution guidelines ziglings should be self contained, which this broke for me.
That is unless I missed something in an earlier zigling that explained this.
The text was updated successfully, but these errors were encountered: