Closed Bug 1673830 Opened 4 years ago Closed 4 years ago

NativeObject methods sometimes specifies slot ranges with start and end index, sometimes with start and length

Categories

(Core :: JavaScript Engine, task, P3)

task

Tracking

()

RESOLVED FIXED
84 Branch
Tracking Status
firefox84 --- fixed

People

(Reporter: jonco, Assigned: jonco)

Details

Attachments

(1 file)

Minor tidyup. We should pick one format and stick to it.

Currently some slot ranges are specified with start and end (exclusive), and
some with start and length. I think the former works out slightly simpler.

Pushed by jcoppeard@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b9dcf577f517
Specify NativeObject slot ranges with start and end index, rather than start and length r=jandem
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 84 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: