Open
Bug 1155457
Opened 9 years ago
Updated 2 years ago
nsTString classes don't support move semantics
Categories
(Core :: XPCOM, defect)
Core
XPCOM
Tracking
()
NEW
People
(Reporter: seth, Unassigned)
Details
We should make nsTString classes support move semantics; they're used all over the place.
Under the hood they do some very similar stuff by passing refcounted nsStringBuffer around. I guess we could save an AddRef/Release pair in most cases?
Reporter | ||
Comment 2•9 years ago
|
||
(In reply to Ben Turner [:bent] (use the needinfo flag!) from comment #1) > Under the hood they do some very similar stuff by passing refcounted > nsStringBuffer around. I guess we could save an AddRef/Release pair in most > cases? Yeah, seems like a small but probably still worthwhile win. There's also a semantic difference between move and copy which usefully clarifies the intent of the code, I think.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•