Christian Buttner
Christian Buttner
It's fixed, thanks.
Just some thoughts. A question to ask is whether this would just be some syntactic sugar where it just wraps come constants in a namespace, or would it pull some...
Yeah, good points. Now I'm questioning what else reflection would even be useful for.
Even though this: ```c module baz; distinct Foo = inline int; const Foo ABC = 3; const Foo BCE = 123; ``` is technically a solution, it has the following...
The enums with associated values is interesting as well, but it looks less intuitive, and it's usefulness seems to be limited to C interop. It's potentially more error prone too,...
> Unfortunately Foo::ABC and Foo.ABC both require modeling it as a separate type. Ah okay, I didn't know the cost was this high. So what's left is the original idea...
`[foo]` is good and intuitive (feels like a common syntax for references). There should be something analogous to Markdown backticks though so you can add code examples without having to...
Some notes: For points 1. and 2. I think it's fine to start with limiting to identifiers that are visible to the current module and see how it works out?...
`base_type` is not bad but it's also not super clear, just from the name alone one might think it returns the underlying type of an enum or optional, or it...
Yeah unfortunately the query files are incompatible with Helix. I suspect a new set of query files have to be made for Helix specifically. I can look into it when...