3 ms·

That seems wrong? For exactly the reason you say. The correct code, I would guess, should be `@This()` However, I also wouldn't be surprised if somehow the m

That seems wrong? For exactly the reason you say. The correct code, I would guess, should be `@This()` However, I also wouldn't be surprised if somehow the memoization in the zig compiler makes this ok

sctb 2y ago
No, it's fine because the 'next' struct member is just a pointer which has a known representation.
- xg15 2y ago
  Ah, so the * type function can "lazily evaluate" its argument?
  - mlugg 2y ago
    It's not actually about `*` -- for instance, declaring `const T = *T;` emits an error. The thing that makes this okay is that field types (for structs and unions) are evaluated in the "lazy" way you describe.
    - xg15 2y ago
      Ah, that makes sense. Thank you!