Elixir v1.11 will be released in October 2020

It also gives us an opportunity to evaluate if every 9 months is a better release frequency than every 6 months.

This is a great idea. Every 6 months might have been the correct cadence while the language was being developed but now that it’s “done” (and I love that decision btw) a slower cadence seems appropriate to consider.

Agreed!

Stability is a feature. Happy to keep it that way.

Great news. 1.10 release was a hard one (IMO comparable to 1.7 and 1.4) on GitHub - elixir-lsp/elixir-ls: A frontend-independent IDE "smartness" server for Elixir. Implements the "Language Server Protocol" standard and provides debugger support via the "Debug Adapter Protocol" · GitHub and GitHub - elixir-lsp/elixir_sense: Provides context-aware information for code completion, documentation, go/jump to definition, signature info and more · GitHub. Some things are still broken on as of 1.10.3 and there are initial reports of further breakage on 1.11-dev.

Right. We need to find a long term approach to bring some of those features into Elixir, so you don’t have to rely on private APIs. Part of it was done with compilation tracers but there is most likely more.

Have you done a talk or a writeup of how these are being brought into Elixir core?

No because there is nothing being done besides it being something we would like to have some day.

I’m just trying out the new xref improvements and while it’s great to be able to see exactly which modules will be recompiled it’s still quite a bit of manual work to find out why a certain module is even linked to the module, which has a compile time dependency to some other module, which will be recompiled. It would be really great to also have means of requesting all the paths between file x and file y.

Thank you for giving master a try @LostKobrakai! However, I am afraid I cannot really act on your feedback. Can you say which commands you tried? Which parts of their output was confusing? You can also find the graphs between two files by using one of them as source or as a sink and then looking at the graph.

I did use mix xref graph --sink …/notifications.ex --label compile to find out a file where I implement Phoenix.Param for some schemas will be recompiled.

…
lib/connect_web/protocols/param.ex
└── lib/connect/externals/sales_responsible.ex (compile)

Generally those those two files shouldn’t have anything to do with each other. But it seems there’s some level of transient dependency here. But it’s not shown completely. sales_responsible.ex aliases team.ex (an ecto belongs_to relationship; I tried Module.concat on it and it removes the dependency) and from there it becomes fuzzy where exactly the path to notifications.ex actually is. I can’t really remove the compile time dependency here as a protocol implementation does require it, but I’d still like to clean up my mess of interdependencies at the layer between notifications.ex and sales_responsible.ex.