Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In attempting to explain the difference between TypeCheck and typespecs to others, it can be difficult to remember and communicate those differences. This is an attempt at providing a visual breakdown of what is supported, what is not, and what is extended.
This first attempt will probably need some updates. For example, all of the Standard Library modules with types that are currently not implemented in TypeCheck are marked as ❌. Some of these are potentially not intended to ever be implemented anyway.
I considered adding this as an issue, but thought it might be something to consider as an article. Either way or neither are fine with me.