Andrew Kelley

Regarding fuzzing, here are some properties we can test in addition to the obvious ones (i.e. not panicking or crashing) * path independence: regardless of the incremental steps taken along...

The programmer has a choice: leave the field order undefined and give the power to the compiler, or use a _packed struct_ and specify the order themselves. Packed structs are...

> So if I need a guarantee on the order of a structure it has to be packed, > right? Correct. There is also the concept of `export` or `extern`...

> don't make undefined the default behavior. You still going to have padding of course, but the order of fields will be guaranteed. Can you explain the use case where...

> Maybe I'm being too pessimistic here, but my impression is that this complexity would backfire in unpredictable ways if you have it by default. If that happens we can...

> Note for the last part, is this not the same as getting the address of the field in the strut via &? See http://ziglang.org/documentation/#builtin-fieldParentPtr

This issue will now have a meaningful impact on async functions since it applies to all local variables.

Mario coin sound is a great example! For this issue however, it is a chance to exercise a little creativity and produce a unique sound.

Fixed with the merge of LLVM 19 branch in c6ad4521c77372cb52adfb9a52b0854d830fed9c.

Can you share your testing methodology?