jakubtomsu
jakubtomsu
My assumption is that it shouldn't create an array for each member of the `Inner` struct. That's because `using` is currently just a syntactic sugar, plus I often want to...
This might be somewhat related to #2041
@guitarvydas This should be fixed now
This might be related to https://github.com/odin-lang/Odin/issues/3514 because the compiler attempts to use the internal pointers as members in the initializer list
Yeah I think it would totally make sense to limit it to procs with only one parameter
Oh, are you planning to eventually support compute shaders, on selected backends? That would be absolutely amazing, it's probably the number one feature I'm missing in sokol_gfx right now. Especially...
> the compiler can't know what type you're specifying in order to know which overload you're asking. Since `a` is the first parameter, the compiler definitely could figure out which...
Right, if this doesn't work with the acessor syntax that's fine, I'm mainly looking for _some_ way to get to get the slice easily. I understand the SOA fields aren't...