tkachuk-labs
Hello! Basically I want to express couple of types/specs. Type parametricity is working for types:
@type functor(a) :: functor(a)
@type either(a, b) :: {:error, a} | {:ok, b}
But is not working for specs. This will not compile for some reason:
@spec fmap((a -> b), functor(a)) :: functor(b)
I don’t want to define a and b. I want them to be generic - just some type a, and some type b which might be not equal to type a.
Another question is how to do shrinking and negation on type level, for example:
@type thunk ???
@type not_a_function ???
@type curried :: (term -> curried | thunk | not_a_function)
@spec curry(function) :: curried | thunk
where thunk is a function of arity equal to zero, and not_a_function is any type except function.
Thanks for your attention.
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
At WyeWorks, we believe great software is built by combining technical excellence with genuine human connection
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
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #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.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Producing high quality Elixir screencasts since 2017.
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)
rodrigues
Hi @tkachuk-labs !
I think you might want to do this:
@spec fmap((a -> b), t(a)) :: t(b) when a: term(), b: term()About the thunk, you can do
(-> integer())for zero arity.Recommend you these docs: Typespecs reference — Elixir v1.20.2
tkachuk-labs
Thanks for reply and the link! I didn’t know about special syntax for zero arity function specs, it looks cool!
Also I didn’t know about guard expressions on type level, that’s awesome! Still a bit confusing, because if we will apply equational reasoning, we will get
which should not be the case for
fmapal2o3cr
Typespecs are not Haskell-style types; trying to reason about them like they are is going to lead to confusion.
In
@spec fmap((a -> b), t(a)) :: t(b) when a: term(), b: term(),termis acting as a bound - and a very loose one at that, as literally anything will satisfy it. This spec will be satisfied iffmapis given any one-arity function and any value, and promises that it will return any value.The Erlang documentation for types can help explain this - the
:operator in that when (spelled::in Erlang) has a particular meaning and it isn’t equality: