mardukbp
I just watched The Ultimate Conditional Syntax, which is about a new syntax for conditional expressions, that is being developed for the new functional programming language MLScript. According to the video “MLScript generalizes ML-style principal type inference to Boolean-algebraic subtyping with first-class union, intersection, negation, and literal types”. This reminded me of the ongoing research on developing set-theoretic types for Elixir.
For example, the following function has type f: (0 | 1) -> ("A" | "B")
fun f(x) = if x is
0 then "A"
1 then "B"
The idea of the authors is to generalize if-then-else to subsume pattern matching. And I think this is also a point of contact with Elixir, which relies heavily on pattern matching.
Maybe this video can provide some food for thought for the future development of Elixir, or maybe it will inspire someone to write a macro. Anyway, I think it is worth sharing with the Elixir community.
Where Next?
Trending in Discussions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
We build reliable cloud platforms for business-critical systems.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixir-ls
- #ai
- #elixirconf-us
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
al2o3cr
Quick reaction before watching the video: other than the spelling, I’m not sure how the example above is different from:
If I read the latter in a module, I might say the former when explaining that function to another person.
al2o3cr
Followup after watching: I’m not sold on the particular syntax - the “operator splitting” in particular seems like the sort of thing that works great for code that fits on a slide but gets weird at larger scale.
The paper mentioned at the end sounds quite a bit more interesting, although Erlang’s type system doesn’t have the specific behavior mentioned on the “MLScript’s Type System and the UCS” -
{:ok, Ecto.Schema.t()} | {:error, Ecto.Changeset.t()}is firmly distinguished from{:ok | :error, Ecto.Schema.t() | Ecto.Changeset.t()}.heilong
The example is equivalent to the simple existing form: