Peter Saxton

*Note to self* this probably also works as a way to get any compiletime values in to the program. Such as when it was compiled, or what the git hash...

Using a module inspired syntax allows two nice things ```rust import gleam/env.{Config as MyConfig, read as do_the_lookup} ``` I think if you restrained the item inside the angles to always...

Further reasons for having a type provider be called only once: Importing the same "provided" module in two places in the code should use the end up with the same...

## Naming. Elixir and Lisps have codegen macros Rust and Go have build hooks F# has type providers OCaml has PPX I wonder if they could be called generated/derived modules...

Further work on Type providers as an external step https://github.com/midas-framework/gleam_providers

Further comments > "you either have to generate another language, or fire up the beam. the first means maintaining another target, the second means significant compile time slowdown" We now...

https://github.com/midas-framework/erlang_library_runtime

is the shorter option for nested if's something like: ```rust case a == 1, b == 2 { True, True -> True, False -> False, _ -> } ``` My...

Fair enough. I reckon a link is still worth having because I don't think it's mentioned that you can destructure in let's anywhere. Unless it's a deliberate choice to lead...

Related question, is there a Gleam version of the Gleam AST? my understanding is that it's all in Rust at the moment.