Cody Tapscott

Thanks! Can you also share the faulty stack trace? It'll help me check that the symbols can be looked up properly (I just need the list of addresses printed)

Looks like the first entry is actually `memcpy` in libc. Lookup fails because Zig builds libc without debug symbols. There are ways for Zig to get those debug symbols (by...

Oh, I see. Looks like it works with `@ptrCast(*const anyopaque, &(&x))` I'll change this to consider adding an error message pointing out the explicit cast. Thanks for the clarification!

It's not obvious to me how to best fix this. Tuple fields are all inferred to be comptime in a comptime context, but this ends up restricting the mutability of...

Would that restriction be "upwardly" viral, so that tuples can't be put in any mutable container or be the target of a mutable pointer? Seems like that would mean some...

What do you think of the alternative solution of treating `var` in a comptime context differently than `comptime var`? The main idea would be that only explicitly comptime objects (i.e....

> However, I'm unsure if `getStringOffset` is correct as I'm unsure how to test it. At the very least it won't cause a regression as the current behaviour is that...

Out of curiosity, how much does this overlap with Return Value Optimization under C-style semantics? Are there cases where this goes beyond what the optimizer can do on its own...

Thanks for those helpful examples. I was having trouble grokking the impact of RLS without aliasing, but the value is clear now. Sounds like an equivalent way to describe it...

LLVM today reports a better error for this: "LLVM ERROR: Flag output operand is of invalid type". That points us to the actual bug: is_error should be a standard power-of-two...