Closed Bug 1876153 Opened 1 year ago Closed 7 months ago

Add UTF-8 support to js-string-builtins

Categories

(Core :: JavaScript: WebAssembly, task, P2)

task

Tracking

()

RESOLVED WONTFIX

People

(Reporter: rhunt, Assigned: jerome)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

The Encoding API builtin modules defined in the proposal add support for UTF-8 encoding through:

  1. wasm:text-decoder" "decodeStringFromUTF8Array
  2. "wasm:text-encoder" "measureStringAsUTF8"
  3. "wasm:text-encoder" "encodeStringIntoUTF8Array"
  4. "wasm:text-encoder" "encodeStringToUTF8Array"

Per https://github.com/WebAssembly/js-string-builtins/issues/34, we are not doing this for the JS string builtins proposal, and the design of these builtins will likely be re-evaluated later.

Status: NEW → RESOLVED
Closed: 7 months ago
Resolution: --- → WONTFIX
Assignee: nobody → jerome

Hi Jerome, thanks for this patch! As Ben says, I think we'll want to re-evaluate the design of these builtins, so I don't think we can merge this right now. I'm hoping to get js-string-builtins to phase 4 at the next CG, but after that I want to champion another builtins proposal and would be happy to include the text-encoder/decoder stuff in that.

A patch has been attached on this bug, which was already closed. Filing a separate bug will ensure better tracking. If this was not by mistake and further action is needed, please alert the appropriate party. (Or: if the patch doesn't change behavior -- e.g. landing a test case, or fixing a typo -- then feel free to disregard this message)

Hi Ryan,
I understand that you want to get js-string-builtins to move forward rapidly. I hope this patch can be useful for the next builtins proposals.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: