Closed Bug 1576076 Opened 5 years ago Closed 4 months ago

Latin1 strings: Add a Latin1 flavor of JSExternalString

Categories

(Core :: JavaScript Engine, enhancement, P3)

enhancement

Tracking

()

RESOLVED FIXED
122 Branch
Tracking Status
firefox122 --- fixed

People

(Reporter: hsivonen, Assigned: arai)

References

Details

Attachments

(2 files, 1 obsolete file)

To enable buffer sharing of DOM ByteString, let's add a Latin1 flavor of JSExternalString.

Priority: -- → P3
See Also: → 655208
See Also: → 1721413
Severity: normal → S3
Attachment #9232384 - Attachment is obsolete: true

In order to avoid confusion and collision with Latin1 flavor, rename existing
APIs to use UC prefix.
Latin1 flavor usually doesn't have any prefix/suffix, but the next patch uses
ExternalStringLatin1, to avoid another confusion with current UTF-16 APIs.

Assignee: nobody → arai.unmht
Status: NEW → ASSIGNED

Adds:

  • JS_NewExternalStringLatin1
  • JS_NewMaybeExternalStringLatin1
  • IsExternalStringLatin1
  • latin1 methods for JSExternalStringCallbacks

Depends on D194672

Pushed by arai_a@mac.com:
https://hg.mozilla.org/integration/autoland/rev/4b98a0b46db4
Part 1: Rename existing ExternalString APIs to use ExternalUCString. r=sfink
https://hg.mozilla.org/integration/autoland/rev/90b59d83622d
Part 2: Support Latin1Char in JSExternalString. r=sfink
Status: ASSIGNED → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → 122 Branch
Blocks: 1869687
See Also: → 1869688
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: