InKryption
InKryption
That would be pretty fantastic for the modal editor workflow, where you can't goto the definition of a type referenced in the on-hover definition popup.
Is it really necessary that `callconv` be be moved in order to make this change? Why is there an ordering requirement for parameter visibility anyway?
> > I think the language should be simplified so that align and callconv expressions come after the fn keyword and it should not be possible to use comptime parameters...
Option 2 makes more sense for code that actually needs notes - just take a look at `std.hash_map.verifyContext`. Variadic arguments aren't friendly to programmatically-built error notes.
> IMO, within Zig, return values are almost always preferable to out-parameters While I agree it's often preferable, I don't think we should disregard the use case. There are many...
~~I'm not 100% sure all `std.testing` functions should have the same error set? I think it would make more sense to split it up into a bunch of error sets...
> One big drawback of this is that you're adding an invisible comptime parameter which silently adds more instantiations of your functions. I don't think this is actually a very...
Small bikeshed: I think it would make sense to make `ContainerLayout` be a tagged union, wherein the `@"packed"` member is of type `type`, as for any state where the layout...
Speaking as a bit of a layman to the compiler jargon, might I ask what type of code this would allow which currently is not allowed?
Reducing the capacity of a SIMD builtin seems explicitly like a step backwards. You can implement swizzling in terms of shuffling without losing performance, but the same is not necessarily...