[connor-makowski]

Add type_enforced to Dynamic Type Checker List

Related Issue: #155
See: https://github.com/connor-makowski/type_enforced

Why Add it:

• It offers fast O(1) and full O(n) type validation.
• It has 10M downloads (currently 200k / month)
• The project keeps up on issues.
• It has been around about for years.
• It has an extensive test and benchmark suite.
• It is fast enough that benchmarks have to measure the differential between an undecorated and decorated functon call.
• Benchmarks show it is the fastest option out there these days for most common use cases.

Worth Noting: I am the maintainer. Feel free to run your own benchmarks and tests. I would welcome and encourage any feedback.

Contributing Checklist:

[x] If you just created something, wait at least 30 days before submitting. This is to give it some time to mature and ensure it's not just a publish-and-forget type of project.
[x] Search previous suggestions before making a new one, as yours may be a duplicate.
[x] Suggested packages should be tested and documented.
[x] Make an individual pull request for each suggestion.
[x] Use the following format: [package](link) [ ]Description.
[x] Additions should be added to the bottom of the relevant category.
[x] Link to the GitHub repo, not npmjs.com or its website.
[x] Keep descriptions short and simple, but descriptive.
[x] Don't mention python in the description as it's implied.
[x] Start the description with a capital and end with a full stop/period.
[x] Don't start the description with A or An.
[x] Check your spelling and grammar.
[x] Make sure your text editor is set to remove trailing whitespace.
[x] The pull request should have a useful title and include a link to the package and why it should be included.
[x] New categories or improvements to the existing categorization are welcome, but should be done in a separate pull request.

[sobolevn]

Thanks!