-
-
Notifications
You must be signed in to change notification settings - Fork 161
test(9249): opt the blocked-store case into strict mode (#9426 semantics) #9481
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
Merged
+25
−1
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,16 @@ | ||
| **test(9249): opt the blocked-store case into strict mode (#9426 semantics)** | ||
|
|
||
| `reflect_define_property_non_writable_prototype_index_blocks_array_store` | ||
| asserted a `TypeError` from a sloppy-mode script. #9426 made a rejected | ||
| array-element write throw **only in strict mode** — which matches node: | ||
|
|
||
| | | output | | ||
| |---|---| | ||
| | Perry, with `"use strict"` | `TypeError 1 P` | | ||
| | Perry, as written (script) | `no error 1 P` | | ||
| | `node --experimental-strip-types`, same `.ts` | `no error 1 P` | | ||
|
|
||
| Perry and node agree exactly, so the code is right and the expectation was | ||
| stale. The test's purpose — a non-writable inherited index BLOCKS the store — | ||
| is still worth keeping, so it opts into strict mode rather than weakening the | ||
| assertion to the sloppy no-op. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Rewrite this as one final release-note entry.
The fragment currently describes test history, command output, and assertion rationale. State the shipped behavior directly: rejected writes to non-writable inherited array indices throw
TypeErrorin strict mode and silently no-op in sloppy mode.Based on learnings: PerryTS/perry changelog fragments must describe the final shipped behavior as one coherent release-note entry, not development-slice narratives.
Proposed release-note wording
📝 Committable suggestion
🤖 Prompt for AI Agents
Source: Learnings