Closed Bug 156713 Opened 24 years ago Closed 16 years ago

make nsString's APIs take nsAStrings instead of nsStrings

Categories

(Core :: XPCOM, defect, P2)

Product:
Core
Component:
XPCOM
Type:
defect

Tracking

()

Status:
RESOLVED INCOMPLETE
Milestone:
mozilla1.5alpha

People

(Reporter: alecf, Assigned: alecf)

References

Details

(Keywords: perf)

This bug is for converting nsString's APIs like EqualsIgnoreCase to take either nsASingleFragmentString or, if possible, nsAString, parameters. This will allow us to do things like foo.EqualsIgnoreCase(NS_LITERAL_CSTRING("foo")) which will allow us to fix bug 132679.
Blocks: 132679
Status: NEW → ASSIGNED
Priority: -- → P2
Target Milestone: --- → mozilla1.2alpha
mozilla 1.2alpha is more or less done. moving mozilla 1.2alpha bugs out to mozilla 1.2beta
Target Milestone: mozilla1.2alpha → mozilla1.2beta
well, so much for 1.2.. off to 1.3, demand is pretty low for this right now
Target Milestone: mozilla1.2beta → mozilla1.3alpha
moving non-critical 1.3alpha bugs to 1.4alpha
Target Milestone: mozilla1.3alpha → mozilla1.4alpha
mass moving lower risk 1.4alpha stuff to 1.4beta
Target Milestone: mozilla1.4alpha → mozilla1.4beta
Target Milestone: mozilla1.4beta → mozilla1.5alpha
Will this also provide some performance gain?
yep, if people use them properly.
Keywords: perf
OS: Windows 2000 → All
Hardware: PC → All
QA Contact: scc → string
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
Component: String → XPCOM
You need to log in before you can comment on or make changes to this bug.