Refactor Runtime Type Checks to Utilize Value-Derived Type Validation #26
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.
This refactor introduces a significant change to the runtime type checking mechanism across the codebase. Previously, each type had an associated assertion function responsible for validating its values. The new implementation shifts this responsibility to a more dynamic approach where the type is deduced directly from the value, and then it is validated to determine if it is a subtype of the expected type.
Key changes include:
Assert
class: The dedicated assertion functions have been removed, as the logic for type validation is now incorporated within theType
class and related expressions.