Bringing Types to Elixir, at ElixirConf EU piped.video/watch?v=gJJH7a2J…

Elixir v1.18-rc.0 is out and it is a massive and beautiful release. More type system work, built-in JSON, language server listeners, parameterized and group tests, "mix format --migrate" and that's not even all: github.com/elixir-lang/elixi…

🧐

I want to share something I built for the Elixir community: elixirevents.net✨ I want to make it easier to find events like conferences and meetups, to help the community grow. For feature requests or feedback please let me know! 🙏 #myelixirstatus #elixirlang

👀

OH YEAH

While working on a new video with solutions to the previous one, I found ChatGPT's new UI struggles even more with concurrent updates: entries lose state and stick around for too long (see video). If this was a LiveView app, we would be getting so much flak.😅 --- I believe part of the problem here is having separate mutate and fetch requests on every deletion. The first fetch is cancelled when the second one comes up, causing items to stick around for longer. Many said yesterday that you could do the mutation and fetch as a single request, but that leads to other problems, such zombie entries. For example, imagine you delete link1 and link2 within a brief period of time. There is no guarantee the deletion order in the database will match the order the client receives the response, so you may end up with this: 1. (client) request to delete link1 sent 2. (client) request to delete link2 sent 3. (server) deletes link1 and loads a new list (includes link2) 4. (server) deletes link2 and loads a new list (no link1 or link2) 5. (client) receives link2 response 6. (client) receives link1 response So if you choose to use the latest response (link1), you brought link2 back to life. If you say you will use the response from the last request, events 3-4 can be swapped, and now you bring link1 back to life. Another way to solve this is by basically not allowing concurrent requests at all but that can affect the user experience drastically in other ways. Next week I should publish a video explaining how LiveView tackles this. Stay tuned!

I just saw @josevalim's post about the math behind the Elixir programming language's new gradual type system checking out. This post was tremendously exciting for me. Allow me to explain with this too-long post.

Our preprint on proving type safety for Elixir's gradual type system. Feedback welcome! arxiv.org/abs/2408.14345

Please welcome Elixir's official Language Server team: @icecreamcohen (Lexical), @mitchhanberg (NextLS), and @lukaszsamson (ElixirLS) team up to provide a unified language server platform. Read all about it here: elixir-lang.org/blog/2024/08…

Built with @elixirlang and @NervesProject!

👀

You want reliability and easy distribution? Of course. You want flexibility and pattern matching? Cetainly. You want Types?! OK. Ok. @duboc_guillaume delivers in his talk, "Set-theoretic Types: The Theory, The Practice" at @ElixirConf US 2024! 2024.ElixirConf.com/#speaker… #MyElixirStatus #ElixirConf #UpcomingConferences

Building single-file Phoenix LiveView apps just got way easier, announcing Phoenix Playground: dashbit.co/blog/announcing-p… #MyElixirStatus

Well, the new @elixirlang 1.17 caught a bug in a well-tested module in our app! (DecodeException wasn't alias'd) This particular function head was missing a test. +1 for types

The research on Elixir’s type system is a collaborative effort. To highlight the latest release that includes types, the CNRS has published this article (in French) for the broader public!

There is a lot of work ahead, but I'm really happy for this release which contains the first steps to a full type system for Elixir. Hope there will be feedback. :-)

I've just experienced my first typing violation with Elixir 1.17 🤩 #MyElixirStatus

Today Elixir turns 12 years old! 🎉🥳 Let's celebrate with Elixir v1.17-rc, which includes our initial work on set-theoretic types, a brand new duration data type, and support for Erlang/OTP 27. Want to give Elixir a gift? Give it a star on GitHub! github.com/elixir-lang/elixi…

Me when somebody asks the benefits of Elixir's on-going type system work and I tell them that it already caught two bugs (one in Phoenix, one in Livebook) even before release:

Last week we had plenty of type system updates, thanks to @duboc_guillaume adding set-theoretic maps/structs. Here is an introduction to our work: hexdocs.pm/elixir/main/gradu… And here is the updated Elixir v1.17 CHANGELOG with a summary of the new warnings: hexdocs.pm/elixir/main/chang…