Erika Rowland

Matching on `Elixir.` matches on most cases, but not all. In the unlikely scenario where someone wants to use something from the Elixir compiler and bootstrap modules: ```gleam import gleam/io...

I'm personally a fan of enums over booleans. But if booleans are preferred, consider adding `enable_` to any of the following names. Possible names: ```toml force_elixir_runtime="enabled" force_elixir_compilation="enabled" force_elixir_stdlib="enabled" elixir_runtime="enabled" load_elixir_modules="enabled"...

For Javascript this seems to be the path creation function: https://github.com/gleam-lang/gleam/blob/4396f9a38a2439d5c7961f952adeec93bd9db624/compiler-core/src/javascript.rs#L324-L341 It currently assumes that it will be in the top of the project.

There seems to be a similar function in the typescript.rs file: https://github.com/gleam-lang/gleam/blob/4396f9a38a2439d5c7961f952adeec93bd9db624/compiler-core/src/javascript/typescript.rs#L279-L297

I could use this too, I like the current `@internal` proposal.

We already have a notion of `internal` that works this way: ```toml # Modules that should be considered "internal" and will not be included in # generated documentation. Note this...

``` hidden_modules = [...] ``` ```rust @hidden pub type HiddenThing ```

I'm a fan of `whatis`.

I would love this!

This would be the implementation, similar to `send_after`: ```gleam @external(erlang, "timer", "send_interval") fn timer_send_interval(a: Int, b: Pid, c: msg) -> Timer pub fn send_interval(subject: Subject(msg), delay: Int, message: msg) ->...