Version 0.10.7 is released!
Fixes:
- Ensure fixed-maps are checked for superfluous keys (c.f. #96). Thank you very much, @patrikstenmark !
Qqwy
TypeCheck Core Team
3
Qqwy
TypeCheck Core Team
Version 0.11.0 has been released! 
Wooh, this is a big release!
Most important features:
- We now support all of Elixir’s builtin basic types!
- We now support all of the remote types of the Elixir standard library!
- Support for most of the map-type syntactic sugars.
- An optional Credo check to enforce that all your functions have a spec.
Full changelog
Additions
- Support for fancier map syntaxes:
%{required(key_type) => value_type}Maps with a single kind of required key-value type.%{optional(key_type) => value_type}Maps with a single kind of optional key-value type.%{:some => a(), :fixed => b(), :keys => c(), optional(atom()) => any()}Maps with any number of fixed keys and a single optional key-value type.- TypeCheck now supports nearly all kinds of map types that see use. Archaic combinations of optional and required are not supported, but also not very useful types in practice.
- Because of this, the inspection of the builtin type
map(key, value)has been changed to look the same as an optional map. This is a minor backwards-incompatible change.
- Desugaring
%{}has changed from ‘any map’ to ‘the empty map’ in line with Elixir’s Typespecs. This is a minor backwards-incompatible change. - Support for the builtin types
port(),reference()and (based on these)identifier(). - Support for the builtin type
struct(). - Support for the builtin type
timeout(). - Support for the builtin type
nonempty_charlist()andmaybe_improper_listand (based on these)iolist()andiodata(). - Adding types depending on these builtins to the default type overrides. We now support all modules of the full standard library!
TypeCheck.Credo.Check.Readability.Specs: an opt-in alternative Credo check which will check whether all functions have either a@spec!or ‘normal’@spec. (Fixes #102).
Fixes
- The
TypeCheck.Builtinmodule is now actually spectested itself. Some consistency bugs were found and solved as a result.
We’re very near to a stable 1.0 release now.
But that is not all: in the meantime, some great work is being done by @orsinium to increase interoptability with modules which are not part of your own codebase.
In the near future (which will be part of the next release) we’ll be able to extract types from external modules and combine them with the ones explicitly written out using TypeCheck.
Work on this is still in progress; there are some design choices to still be made. If you find this interesting or have opinions about it, please let us know!
20
baldwindavid
Wow, what a massive release! Basically, all green check marks here now… Comparison to Plain Typespecs — TypeCheck v0.13.7
Great work and thanks for pushing the typing options in the ecosystem forward.
6
Qqwy
TypeCheck Core Team
Version 0.12.0 is released!
Additions:
Per-dependency configuration
The default options used are now fetched from the application configuration.
This means that you can configure a default for your app as well as for each of your dependencies(!) by adding config :app_name, :type_check [...] to your configuration file(s).
(This configuration can then further be overridden per module, which was already possible in earlier versions.)
Building types and checks for external functions
If you want to use types from modules outside of your control, until now you had to manually recreate them.
Now, the TypeCheck.External module allows fetching the ‘normal’ types and specs from a compiled module.
Specifically:
-
TypeCheck.Externalmodule, with functions to work with typespecs in modules outside of your control.fetch_specto build a TypeCheck type from any function that has a@spec.fetch_typeto build a TypeCheck type from any@type.enforce_spec!to wrap a call to any function that has a@specwith a runtime type-check on the input parameters and return value.applyandapply!to wrap a call to any function with the function spec type that you give it.
iex> TypeCheck.External.enforce_spec!(Kernel.abs(-13))
13
iex> TypeCheck.External.enforce_spec!(Kernel.abs("hi"))
** (TypeCheck.TypeError) At lib/type_check/external.ex:175:
`"hi"` is not a number.
This functionality is still very new, so we consider it to be a little experimental.
In the near future, it might be integrated further with the rest of the library. For instance, we might add syntactic sugar to make ‘type overrides’ easier.
I want to take this opportunity to thank @orsinium greatly. Both the idea and the implementation of this functionality is his work! 
Defstruct!
TypeCheck.Defstruct.defstruct!, a way to combine defstruct, @enforce_keys and the creation of the struct’s type, reducing boilerplate and the possibility of mistakes. (c.f. #118 )
Example:
defmodule User do
use TypeCheck
use TypeCheck.Defstruct
defstruct!(
name: "Guest" :: String.t(),
age: _ :: non_neg_integer()
)
end
is syntactic sugar for:
defmodule User do
use TypeCheck
use TypeCheck.Defstruct
@type! t() :: %User{
name: String.t(),
age: non_neg_integer()
}
@enforce_keys [:age]
defstruct [:age, name: "Guest"]
end
Fixes:
- Long-standing issue where Dialyzer would sometimes complain in apps using TypeCheck is resolved. (c.f. #95)
- Creation of the new
maybe_nonempty_listtype will no longer get stuck in an infinite loop on creation. (c.f. #120)
This new release is just in time for ElixirConf.EU where I will be speaking about TypeCheck. I look forward to see a lot of you there (live or virtually)!
Assuming they arrive on time, there will also be stickers 
8
Qqwy
TypeCheck Core Team
Qqwy
TypeCheck Core Team
ElixirConf.EU was a lot of fun!
Being with such a nice group of cool, clever and excited people is a really great way to get new energy to continue any project.
Many people asked questions and gave valuable feedback.
Thank you very much, everyone!
(For who was not there: A video recording of the talk will be released some time later in this year, once the organisers are ready to do so.)
16
eksperimental
begedin
Qqwy
TypeCheck Core Team
FYI, currently TypeCheck does not work well with Elixir v1.17.
There is a change in how ... is parsed in the Elixir AST from v1.16 to v1.17, which the TypeCheck library currently does not handle correctly, as it expects the older format.
Unfortunately, I’m on vacation until the start of August, so it might be a while for a fix to be implemented, unless someone is able to contribute a PR in the meantime.
I apologize for any inconvenience!
Qqwy
TypeCheck Core Team
Version 0.13.7 has been released!
This release contains two important fixes:
- Support for Elixir v1.17. Sorry for the long wait. Thank you very much for your help here, @skwerlman!
- Map fields of types are printed in sort order (when inspecting the type and also in runtime type error messages), allowing the usage of TypeCheck in projects that target both OTP 25 (or below) and OTP 26/27 at the same time.