Alright folks, in a nutshell, this release addresses all feedback from the previous RCs:

1. Fully compatible with Erlang/OTP 28.1+

2. Struct update syntax has been adapted into a type assertion operator

3. Addresses issues with projecting taking too long to compile

This should be our final stop before v1.19, please give it a try!

Perfect timing, we were just about to release it. Fixed!

Oh, I think I got it. You literally have a protocol and then in one of the implementations, you define additional clauses.

Yes, the warning is expected. The type system is enforcing that you are implementing the protocol exactly for the type of that implementation. We could not emit any warning, but then it means someone may accidentally define additional clauses, and they won’t get any help from the type system. So we chose to enforce that the first argument matches the implementation.

If the description above is not correct, then please provide a way to reproduce this or post a larger code snippet. Thanks.

I have verified across multiple projects now. We did hit the issue in rc.1
But rc.2 seems solid.

I am deploying to some QA ENVs right now but things look really good.
Probably 20k unit tests across the projects we’ve updated. All passing.
Huge improvements.

THANK YOU SO MUCH!!!

It will do more work because the type system is smarter. So that bit is expected too!