High level library goals

I'm trying to understand this at a very high level. My current understanding is that upon compilation this will be able to uncover issues by inferring types "when it reasonably can" with compiler warnings. When it cannot, standard Elixir typespecs can be used to give the library more information to work with. Correct?

That would be plenty, but I'm wondering if there are plans for further ways to specify more complex types that typespecs cannot handle. Basically, will it handle any extended syntax that traditional typespecs might not? I'm not even sure that it should, but one thing that has been handy with the TypeCheck runtime checker is that it supports any custom Elixir (for better or worse).

This issue is a high-level question about inferred types, Elixir typespecs, and possible extended type syntax. No files, tests, entry points, implementation scope, or completion criteria are identified, so clarification of the intended project change is needed before work can begin.

Written by the indexing model from the issue text.