On 01/09/2014 03:33 AM, Neil wrote:
> This does not apply to AssignLiteral on an nsString, since that used to
> take a char (&)[] parameter. Instead, consider assigning an
> NS_LITERAL_STRING, or you can also use the new char16_t overload of
> AssignLiteral by wrapping your string constant in MOZ_UTF16().
Just to be clear -- does this mean we should strictly prefer
str.Assign(NS_LITERAL_STRING("foo")) over str.AssignLiteral("foo") now?
(If so, that's an important recommendation to call out. I believe we
previously were recommending that folks use AssignLiteral, since it's
more concise and (until now) didn't have any downsides as compared to
the longer-form version, AFAIK.)
Thanks!
~Daniel
_______________________________________________
dev-platform mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-platform
