Gears

You would want to look at the `run` module inside `compiler-cli`. It would probably be around [this line](https://github.com/gleam-lang/gleam/blob/d292718f34d5ce2edbb1ae704712f9cc46fbc14e/compiler-cli/src/run.rs#L124), where the main function is retrieved. Currently, the `ModuleFunction` struct only contains...

That makes sense to me. We already do that for unqualified imports

We already have the code for document symbols within a single file, so after that is figured out, the rest of the code should already be there

The LSP specification seems [incredibly vague](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspaceSymbolParams) on how the actual request works. I would suggest only showing symbols for the root package, and not dependency packages. It is quite a...

I'm pretty sure you can re-open it yourself

The referenced issue has now been resolved so this PR should probably be closed

1. No, the user isn't guaranteed to have formatted their code before running a code action. What we usually do when a certain new piece of location information is required...

There isn't much documentation on the structure of the project unfortunately. I was working on some but it never got to a finished state. You're welcome to try this issue...

Looks like it's failing from this line of the stdlib: https://github.com/gleam-lang/stdlib/blob/main/src/gleam/bit_array.gleam#L70 On Erlang, `_:utf8` is the same as `_:utf8_codepoint`, so I guess that's why the issue wasn't caught until now.

Seems like it yes. In that case would this be considered a breaking change? Or will we treat it like a bug which was never intended?