don't allocate nsCStrings when doing integer parsing

RESOLVED FIXED in Firefox 60

Status

()

enhancement
RESOLVED FIXED
Last year
Last year

People

(Reporter: froydnj, Assigned: froydnj)

Tracking

unspecified
mozilla60
Points:
---

Firefox Tracking Flags

(firefox60 fixed)

Details

Attachments

(1 attachment)

There's no need to allocate a completely new nsCString when all we want
to do is parse a character string into an integer.  We can allocate a
dependent string instead, which will avoid some memory churn.
We should really be parsing the `const char*` directly, but one step at a
time...
Attachment #8956933 - Flags: review?(michal.novotny)
Attachment #8956933 - Flags: review?(michal.novotny) → review+
Pushed by nfroyd@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/0f64845d179b
don't allocate nsCStrings when doing integer parsing; r=michal
https://hg.mozilla.org/mozilla-central/rev/0f64845d179b
Status: NEW → RESOLVED
Closed: Last year
Resolution: --- → FIXED
Target Milestone: --- → mozilla60
You need to log in before you can comment on or make changes to this bug.