-
Notifications
You must be signed in to change notification settings - Fork 1
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
Document the permanent bidirectional stability of immutable ArrayBuffer contents #44
Conversation
…e ArrayBuffer contents
The rendered spec for this PR is available at https://tc39.es/proposal-immutable-arraybuffer/pr/44. |
spec.emu
Outdated
@@ -416,7 +416,7 @@ contributors: Mark S. Miller, Richard Gibson | |||
</h1> | |||
<dl class="header"> | |||
<dt>description</dt> | |||
<dd>It is used to create an immutable ArrayBuffer (i.e., an ArrayBuffer with a an [[ArrayBufferIsImmutable]] slot) with contents from _fromBlock_.</dd> | |||
<dd>It is used to create an immutable ArrayBuffer (i.e., an ArrayBuffer with a an [[ArrayBufferIsImmutable]] slot) with contents from _fromBlock_. The contents of an immutable ArrayBuffer's Data Block are constrained to be permanently stable, and may not be modified by either ECMAScript code or by other activities that may take place inside an implementation or observable by it.</dd> |
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.
Grammar?
<dd>It is used to create an immutable ArrayBuffer (i.e., an ArrayBuffer with a an [[ArrayBufferIsImmutable]] slot) with contents from _fromBlock_. The contents of an immutable ArrayBuffer's Data Block are constrained to be permanently stable, and may not be modified by either ECMAScript code or by other activities that may take place inside an implementation or observable by it.</dd> | |
<dd>It is used to create an immutable ArrayBuffer (i.e., an ArrayBuffer with a an [[ArrayBufferIsImmutable]] slot) with contents from _fromBlock_. The contents of an immutable ArrayBuffer's Data Block are constrained to be permanently stable, and may not be modified by either ECMAScript code or by other activities that may take place inside an implementation or be observable by it.</dd> |
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.
Is it not that the contents must never be observably modified, specifically from the perspective of ecmascript code? in practice that would still mean the host can't modify the backing memory.
This is strictly speaking normative. (I claimed otherwise earlier but was mistaken.) |
Given @bakkot 's later point, that the rest of the spec as a whole still does not imply immutability, and therefore that this change is normative, I'm removing the term "Editorial: " from the title. |
…mmutable ArrayBuffer contents
This merge was somehow lost, and has been restored as 83479c9. |
I might have lost it with late-night "git push --force" steps when, in retrospect, I was too tired to do such things. Sorry! If you can, please check if I accidentally wiped out anything else. Thanks! |
All of the other PRs seem to still be in place, but direct pushes to |
https://github.com/tc39/proposal-immutable-arraybuffer/activity?ref=main only shows a single force push that doesn't seem to have erased anything. |
No description provided.