Closed Bug 1559177 Opened 5 years ago Closed 2 years ago

Structured cloning should have a JS_WriteDouble

Categories

(Core :: JavaScript Engine, task, P3)

task

Tracking

()

RESOLVED FIXED
100 Branch
Tracking Status
firefox69 --- wontfix
firefox100 --- fixed

People

(Reporter: bzbarsky, Assigned: caroline)

Details

Attachments

(2 files)

For that matter, having a public API to write doubles would be nice too, I suspect.

For now, the code in bug 1420580 is hand-rolling this via bitwise casts to uint32_t, which I think works correctly, modulo not doing any NaN canonicalization. But it's not 100% clear whether we'd want NaN canonicalization in these APIs.

Yeah, we need a JS_WriteDouble too, in bug 1420580.

Summary: Structured cloning should have a JS_WriteFloatPair → Structured cloning should have a JS_WriteFloatPair and JS_WriteDouble

Prioritizing cross-team requests is hard. How many beers is this worth?

Flags: needinfo?(bzbarsky)

Good question. This is not blocking anything, but it would be nice to clean up the code, basically. Let's say 1 beer? ;)

Not urgent, but would be nice.

Looks like we don't need the "two floats" option anymore, just the "write a double" option.

Flags: needinfo?(bzbarsky)
Summary: Structured cloning should have a JS_WriteFloatPair and JS_WriteDouble → Structured cloning should have a JS_WriteDouble
Priority: -- → P3
Assignee: nobody → ccullen
Status: NEW → ASSIGNED

Caroline, I won't be able to review this, so having me as a blocking reviewer is not a great idea.

Depends on D142585

Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 100 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: