Tynan Beatty
Tynan Beatty
Current formatter (v1.0.0-rc2) produces this ```gleam let #(prompt, default, to_bool) = case default { True -> #( // break it up prompt " (Y/n)", "y", fn(x) { !string.starts_with(x, "n") },...
As mentioned in https://github.com/gleam-lang/mix_gleam/issues/38 The `gleam compile-package` API should perhaps not generate these warnings, or have a flag to disable them.
This Gleam ```gleam fn a() { case [] { [..] -> 1 _ -> 2 } } ``` Produces this Erlang in Gleam v1.0.0 ```erlang -spec a() -> integer(). a()...
This Gleam ```gleam fn b() { { use a { return a; }) ((cb) => { return cb(2); })((b) => { return b; }) return 3; } ``` Causing this...
This should allow the "Manually run" button to work every time as expected.
```typescript const $Foo = $interface({ url: $optional($string) }); type Foo = Type & { [index: string]: unknown; }; const data: Foo = { notUrl: "any" }; //
The following function head (82 characters) could be wrapped, but currently (since before Gleam v1.3.0) the formatter keeps it all on one line. ```gleam fn do_menu_items(acc: Queue(MenuItem), from tasks: List(Task))...