Switching to Elixir

Re:Switching to Elixir by keep_reading on Friday November 10, 2023 @09:54AM (#38219577)

While you're waiting for official support in the language, just properly document functions with @spec and change them to @spec! after adding TypeCheck to your project and viola, you get powerful type checking at runtime with almost no performance impact. The error messages it produces are so beautiful.

https://github.com/Qqwy/elixir-type_check

[ Parent | on HN ]

Re:Switching to Elixir by conradfr on Friday November 10, 2023 @10:52AM (#38220370)

In a functional language where you're writing a lot of functions it's a bore and feel very dated.

Especially as you have to write the function name so copy/paste from other @spec doesn't really at least speed it up.

It is what it is I guess.

[ Parent | on HN ]

Re:Switching to Elixir by keep_reading on Friday November 10, 2023 @11:42AM (#38221031)

well, you can avoid this if you try to limit the number of public functions so you don't have to do this as often. make as many defp functions as possible, really.

[ Parent | on HN ]

Re:Switching to Elixir by satvikpendem on Friday November 10, 2023 @11:08AM (#38220563)

> and viola

Nice to see you are a musical aficionado too. More seriously, how does this compare to other type checking alternatives for Elixir/BEAM were I to start a new project, including Gleam and Witchcraft (which at least seems to be unmaintained for now)?

[ Parent | on HN ]