Closed Bug 1621386 Opened 5 years ago Closed 5 years ago

Add a way to convert strings to JS char16_t sequences without allocating memory

Categories

(Core :: JavaScript Engine, task, P1)

task

Tracking

()

RESOLVED FIXED
mozilla76
Tracking Status
firefox76 --- fixed

People

(Reporter: djvj, Assigned: djvj)

References

Details

Attachments

(1 file)

This is in support of the ParserAtoms work in bug 1592105.

To avoid unnecessary memory allocations when designing the parser-internal atoms table, we need a way of seamlessly iterating over character sequences as if they were sequences of char16_ts, without allocating memory for conversion.

The input character sets that need support are UTF8, Latin1 (both 8-bit character units), and char16_t.

The first two will need decoding/conversion of some sort, but the last case should be a simple pass-through iterator over the source characters.

Assignee: nobody → kvijayan
Status: NEW → ASSIGNED
Priority: -- → P1
Attachment #9132384 - Attachment description: Bug 1621386 - Add a way to convert strings to JS char16_t sequences without allocating memory. r=jwalden → Bug 1621386 - Add a way to convert strings to JS char16_t sequences without allocating memory. r=djvj
Attachment #9132384 - Attachment description: Bug 1621386 - Add a way to convert strings to JS char16_t sequences without allocating memory. r=djvj → Bug 1621386 - Add a way to convert strings to JS char16_t sequences without allocating memory. r=djvj!
Pushed by jwalden@mit.edu: https://hg.mozilla.org/integration/autoland/rev/9c1fa3e6e991 Add a way to convert strings to JS char16_t sequences without allocating memory. r=djvj
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla76
Depends on: 1626767
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: