You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before we introduced a Tuple type for fixed-size array, we used to enforce the correct size of object members of type array using some calls to assertMemberLength() in the constructor.
In between, a lot of such arrays were migrated into Tuples.
Therefore, passing an array or a Tuple of the wrong size would be detected at compile-time and therefore the use of assertMemberLength() is not needed anymore.
One might argue that maintaining assertMemberLength() use would detect abuse of type casting like 'array as Tuple<>' though.
The text was updated successfully, but these errors were encountered:
Resolves#2295
# Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if
the PR is ready to merge.
- [x] If the pull request requires a cryptography review (e.g.
cryptographic algorithm implementations) I have added the 'crypto' tag.
- [x] I have reviewed my diff in github, line by line and removed
unexpected formatting changes, testing logs, or commented-out code.
- [x] Every change is related to the PR description.
- [x] I have
[linked](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue)
this pull request to relevant issues (if any exist).
Before we introduced a Tuple type for fixed-size array, we used to enforce the correct size of object members of type array using some calls to assertMemberLength() in the constructor.
In between, a lot of such arrays were migrated into Tuples.
Therefore, passing an array or a Tuple of the wrong size would be detected at compile-time and therefore the use of assertMemberLength() is not needed anymore.
One might argue that maintaining assertMemberLength() use would detect abuse of type casting like 'array as Tuple<>' though.
The text was updated successfully, but these errors were encountered: