tgschultz
tgschultz
I've been writing a Gigatron emulator as a side project and ran across what I believe to be this same issue. Naturally I first thought it was an issue with...
I can confirm that this is a comptime issue by making all the comptime references to the interface runtime instead and indeed tests now appear to run fine. Additionally I...
One objection I can think of to handling these as opaque types is that `@distinct(T)` as envisioned originally would be useful for C-style flags, and `@OpaqueHandle(T)` wouldn't because you can't...
It's possible to do this using definitions: ``` pub const Compression = extern enum(u32) { Uncompressed = 0, RLE8 = 1, //8bpp only RLE4 = 2, //4bpp only Bitfields =...
One thing that was mentioned in IRC is that this would allow storing comptime metadata in comments and changing program behavior based on it. I think we can all agree...
There are actually quite a few places where the std lib breaks formatting guidelines or is generally inconsistent. For example, many fields in the structs produced by `@typeInfo` are snake_case...
This is not the behavior I would expect when working with big endian. The "first" bit of any given buffer would, to my reckoning, be the highest bit of the...
I believe this is because the socket is not created with ```WSA_FLAG_OVERLAPPED```, which typically sockets are on Windows: > **WSA_FLAG_OVERLAPPED** 0x01 > > Create a socket that supports overlapped I/O...
I've spent some time thinking about this, and I think it might not even be necessary to introduce a new builtin for most cases. Consider that Zig has a zero-sized...