3 ms·
The most useful values at compile time are types, so straight-up interpreting the core language at compile time is not enough. You need meta-typed named values
by ncmncm 6y ago
The most useful values at compile time are types, so straight-up interpreting the core language at compile time is not enough. You need meta-typed named values to transport types in, and meta-functions to pass them to.
Fortraith cleverly re-purposes existing features, doing some violence to language usage conventions to achieve it.
- deleted 6y ago[deleted]
- dependenttypes 6y ago> so straight-up interpreting the core language at compile time is not enough. You need meta-typed named values to transport types in, and meta-functions to pass them to. Can you please explain what you mean by this?
- neutronicus 6y agoIn Rust (for example), Types are not Values. You can't store them in variables, pass them to functions, etc. However, at macro-expansion time, often what you want to do is examine a Type and expand the macro differently based on some information about the Type. So you would like your Macro language to have some notion of manipulating Types that is absent from the language itself