Veikka Tuominen
Veikka Tuominen
This is a best-effort implementation since my understanding of the current accepted semantics for packed structs is a bit hazy and none of the proposals list all the allowed types.
```sh-session $ cat a.c extern char __libc_single_threaded; int main(void) { return __libc_single_threaded; } $ clang a.c $ zig build-exe a.c -lc ld.lld: error: undefined symbol: __libc_single_threaded >>> referenced by a.c:3...
```zig // test.zig pub fn main() void { foo(12, 23.5, .foo, "true"); } fn foo(a: u32, b: f64, c: enum {foo, bar}, d: []const u8) void { _ = a;...
Currently both just default to `1`. Note: the size calculation should happen after the attributes after the type are parsed since they may contain a packed attribute.
We currently store all defined aligned attributes for types but only use the largest. I don't see why this couldn't be normalized when creating the attributed type.
`_BitInt` is coming in C2X and `__i128` is already a widely supported extension so we should support them. The current constant expression evaluation system uses `@opWithOverflow` but it doesn't scale...
The dream would be to have Python like "batteries included" stdlib.
```julia [1,2,3] * 2 # -> [2,4,6] # maybe even [1,2,3] * [4,5,6] # -> [4, 10, 18] ```
`lazy` expressions would be the language level equivalent of `std.once`. The value of the expression would only be executed once and only if needed. These would mainly be beneficial for...