chazwatkins
With Elixir 1.18 nearing release and coming with improvements to the new Set Theoretic Type System, I’m curious how Ash will integrate the new type system. Will it generate the types for domains and resources? Will we get the compilation time feedback from the type system?
Where Next?
Trending in Questions
Other Trending Topics
Latest Ash Threads
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
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.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
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 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
zachdaniel
Currently, all type system improvements are “under the hood” so to speak. There is no real way to influence them except by perhaps us defining functions with clearer returns in cases where the type system cannot yet infer them. i.e ensuring that we pattern match on
%Ash.Query{}etc.However, I’ve spoken with @josevalim about this before, and the type system should be metaprogrammable in the same way that the rest of Elixir is (obviously not holding anyone to this as a commitment, but as I understand it it is the intention).
We currently do not generate dialyzer types except for very simple circumstances like
Ash.Type.Enum, however as soon as it is possible to manually write Elixir’s type syntax, we will begin the process of adopting them across Ash on behalf of users. You should have to do very little to get tons of benefits.All code interfaces will be fully typed automatically to the best extent that we can, and we will provide convenience types and/or functions for use in other scenarios.
There is still a lot of unknowns here, but IMO the type system will be a major leveling up for Elixir and it will especially enable us to do some very awesome things in Ash. It will, however, take a lot of time for that all to come to fruition.
Ash is already chock-full of type information that is used to verify Ash programs and validate data etc, and we intend to take full advantage of the set theoretic type system
chazwatkins
Thanks. I also think the new type system is going to be a major level up.
I suspected type support wouldn’t require any changes from Ash user’s. That’s the power of “deriving the rest”.