Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Return sequences instead of FrozenArrays #119

Merged
merged 1 commit into from
Jun 11, 2024
Merged

Return sequences instead of FrozenArrays #119

merged 1 commit into from
Jun 11, 2024

Conversation

toji
Copy link
Member

@toji toji commented Jun 11, 2024

Fixes #117

As agreed on in today's call, having getHitTestResults and getHitTestResultsForTransientInput return FrozenArrays isn't being used for optimization purposes, and is unusual relative to other Web APIs. This PR changes them both to sequences, which shouldn't result in any user-facing breaking behavior.


Preview | Diff

@toji toji requested a review from bialpio June 11, 2024 21:09
@toji toji merged commit 6b5297b into main Jun 11, 2024
2 checks passed
@toji toji deleted the return-sequence branch June 11, 2024 22:04
github-actions bot added a commit that referenced this pull request Jun 11, 2024
SHA: 6b5297b
Reason: push, by toji

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Use of FrozenArray<>s for return types of methods is probably unnecessary
2 participants