Enhance UnsafePutElements to also work for non-indexed properties

RESOLVED WONTFIX

Status

()

Core
JavaScript Engine
RESOLVED WONTFIX
4 years ago
2 years ago

People

(Reporter: till, Unassigned)

Tracking

(Blocks: 1 bug)

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [js:t])

(Reporter)

Description

4 years ago
We don't need support for performing the [[Put]] operation on anything but indexed elements in self-hosted code, yet. That'll probably change at some point, at which time UnsafePutElements should be changed to support it. And be renamed to UnsafePut.

The other option would be to keep UnsafePutElements as a fast-path for putting arbitrary numbers of indexed elements at once, and introduce UnsafePut in addition.

Comment 1

4 years ago
So the reason for UnsafePutElements supporting arbitrary numbers of indexed elements is for atomicity. I don't know of a use case now, but atomicity could be useful for the generic UnsafePut as well.
(Reporter)

Comment 2

4 years ago
Ah, that makes sense, thanks for the explanation. While I don't know of a use case, either, I'm certainly not opposed to an UnsafePut that works for arbitrary numbers of either indexed elements or named properties.
(Assignee)

Updated

3 years ago
Assignee: general → nobody
UnsafePutElements was removed in http://hg.mozilla.org/mozilla-central/rev/5dbe1acdee3c - Resolving as Won't Fix.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.