Łukasz Samson

To reproduce 1. clone https://github.com/elixir-lsp/elixir_sense 2. in `mix.exs` add `:overspecs` dialyzer flag 3. (optional ) bump dialyxir to github master 4. mix deps.get && mix dialyzer

Nice work @mhanberg but I'm not completely convinced we should go this road. Let me state my reasons. 1. Relying on DocumentSymbols provider is in fact relying on AST parsing...

I already have a PoC branch with DocumentSymbols using a database built by compile tracers. It looks promising but requires more work and integration with current AST based approach. Currently...

Excellent writeup @victorolinasc. I added a small comment on code loading. Can you create a PR with this wrapped as `.md` documentation. I guess it's going to be useful to...

I’ll take a look but I won’t have time to make any tests. I wonder if an incremental approach wouldn’t complicate things too much.

This comment suggests a workaround for the problem with dependencies https://github.com/JakeBecker/elixir-ls/issues/97#issuecomment-406243067

It could work with if there's a sane fallback to default build. I fear that as @axelson said we'd have to deal with a slew of bugs from older elixir-ls...

@Benjamin-Philip > I have been procrastinating in making the switch from alchemist.el for a few months now. I realised that the main reason that I have not made the switch...

@Benjamin-Philip for reference I looked up the PR and issue that removed escripts https://github.com/JakeBecker/elixir-ls/issues/12 https://github.com/JakeBecker/elixir-ls/pull/13 While it would be trivial to build and publish escripts to mix it stil does...

@TheFirstAvenger do you have a reliable way of reproducing it? I hit similar errors with mix but they are difficult to reproduce.