Closed
Bug 1791357
Opened 2 years ago
Closed 2 years ago
Consistently use char32_t for code points
Categories
(Core :: JavaScript Engine, task, P1)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
107 Branch
| Tracking | Status | |
|---|---|---|
| firefox107 | --- | fixed |
People
(Reporter: anba, Assigned: anba)
Details
Attachments
(2 files)
We're currently using char32_t and uint32_t for code points. Let's switch to using only char32_t.
|
Assignee | |
Comment 1•2 years ago
|
||
|
|
Assignee | |
Comment 2•2 years ago
|
||
Consistently use char32_t when referring to code points instead of using
sometimes char32_t and in other places uint32_t.
Depends on D157622
Pushed by andre.bargull@gmail.com: https://hg.mozilla.org/integration/autoland/rev/56d2fac4f906 Part 1: Remove unused out-params for TokenStreamSpecific::get{,FullAscii}CodePoint. r=arai https://hg.mozilla.org/integration/autoland/rev/b80a69683a73 Part 2: Use char32_t instead of uint32_t for code points. r=arai
|
||
Updated•2 years ago
|
Priority: -- → P1
|
||
Comment 4•2 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/56d2fac4f906
https://hg.mozilla.org/mozilla-central/rev/b80a69683a73
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 107 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•