Giacomo Cavalieri

`gleam test` doesn't check it can actually run the tests on given target

2

When running `gleam test` it looks like it doesn't check if it can run the tests on the given target so for example with this one: ```gleam pub fn wobble_test()...

Fix a bug where a record constructor's argument would not have a doc string

7

This issue closes #2631

Replace use detection with a call graph

3

I noticed that a private recursive function is not marked as unused. For example this one raises no warnings: ```gleam fn wobble() { wobble() } ```

In this snippet of code ```gleam pub type Wibble { Wobble( /// Documentation!! wabble: Int, ) } pub fn main() { io.println("Hello from prova!") } ``` The generated documentation looks...

Inconsistent type variable names in generated documentation between types and functions

3

Hello! I noticed something in the documentation that is bugging me. Take this piece of code: ```gleam pub opaque type Graph(direction, value, label) { Graph // This is not relevant...

This PR closes #2617 This is a WIP because it's waiting for the testing issue in #2635 to be fixed

Add internal annotation

6

This PR adds the `@internal` annotation, closing #2486 ### ~~Why is this a WIP PR?~~ - [x] I'm waiting for #2537 to be merged and exclude internals from the package...

This PR closes #727 The formatter: - Preserves comments - Uses comments/empty lines to tell groups apart and sort those separately - Sorts all imports of each group alphabetically

Unbound type variable in top level definition after type inference

1

In this case, after type inference, the `main` function ends up having an inferred type with an unbound type variable instead of a generic one: ```gleam pub type Foo(a) {...

Show helpful error message if trying to append to a string using the spread operator

1

Some newcomers try doing this `[..wibble, item]` to append an item to a list expecting it to work like prepending does. The error message is not particularly useful as it...