In modern C++, static constexpr member variables are automatically
inline (aka weak) so the template trick is not needed. This also avoid
duplication and reduces the amount of parsed code. No impact on
generated binary (actually: smaller debuginfo, close to identical
binary).
Differential Revision: https://phabricator.services.mozilla.com/D247825
XSLT was the last consumer of this method.
After its migration to Fluent, it is not needed anymore.
Also, remove properties files that were used only by
FormatStatusMessage.
Differential Revision: https://phabricator.services.mozilla.com/D245696
XSLT was the last consumer of this method.
After its migration to Fluent, it is not needed anymore.
Also, remove properties files that were used only by
FormatStatusMessage.
Differential Revision: https://phabricator.services.mozilla.com/D245696
Add ICU4X based calendars for Chinese and Dangun to ensure consistent behaviour
across `Intl.DateTimeFormat` and `Temporal`.
This requires using the ICU4C C++ API, so it's not possible to use when
`MOZ_SYSTEM_ICU` is defined. And ICU4X's calendar FFI needs to be available,
which is currently guarded by `JS_HAS_TEMPORAL_API`.
Differential Revision: https://phabricator.services.mozilla.com/D241645
Always reset the Gregorian change date, because all uses either require the
Gregorian change date to be set to `-8.64e15` or don't care about dates far
into the past.
The slow `DateIntervalFormat::TryFormatCalendar` is now only used when
`MOZ_SYSTEM_ICU` is defined.
And also resets the Gregorian change date for "buddhist", "japanese", and
"roc" to get consistent results when compared to the ICU4X-based Temporal
code.
Differential Revision: https://phabricator.services.mozilla.com/D241644
Add ICU4X based calendars for Chinese and Dangun to ensure consistent behaviour
across `Intl.DateTimeFormat` and `Temporal`.
This requires using the ICU4C C++ API, so it's not possible to use when
`MOZ_SYSTEM_ICU` is defined. And ICU4X's calendar FFI needs to be available,
which is currently guarded by `JS_HAS_TEMPORAL_API`.
Differential Revision: https://phabricator.services.mozilla.com/D241645
Always reset the Gregorian change date, because all uses either require the
Gregorian change date to be set to `-8.64e15` or don't care about dates far
into the past.
The slow `DateIntervalFormat::TryFormatCalendar` is now only used when
`MOZ_SYSTEM_ICU` is defined.
And also resets the Gregorian change date for "buddhist", "japanese", and
"roc" to get consistent results when compared to the ICU4X-based Temporal
code.
Differential Revision: https://phabricator.services.mozilla.com/D241644
After landing bug 1733498, `necko.properties` has no status error message.
Also, network module doesn't use `FormatStatusMessage` now.
We should remove NS_ERROR_MODULE_NETWORK support from `FormatStatusMessag`.
Differential Revision: https://phabricator.services.mozilla.com/D245178
This diff was generated as follows:
List all toml files in the tree:
`find * -name '*.toml' > /tmp/toml`
Manually edited /tmp/toml to drop non-relevant entries (objdir).
Ran the toml linter for all files:
`cat /tmp/toml | xargs ./mach lint -l test-manifest-toml --fix`
Differential Revision: https://phabricator.services.mozilla.com/D240948
`JS_HAS_INTL_API` and `MOZ_ICU4X` are always set unless building js-standalone
packages. And because "intl/lwbrk" isn't used for js-standalone packages, both
options (`JS_HAS_INTL_API` and `MOZ_ICU4X`) are guaranteed to be defined.
Differential Revision: https://phabricator.services.mozilla.com/D245272
We don't need this param; it should be safe to call the method from any thread
and just rely on its internal locking to protect the cache.
Differential Revision: https://phabricator.services.mozilla.com/D245357
Update language tag mappings by running `./make_intl_data.py langtags`.
CLDR download URL was changed and no longer includes the trailing ".0".
Differential Revision: https://phabricator.services.mozilla.com/D241785
This disarms a footgun in the FreezableMapping::Freeze API, which was
causing read-only mappings in the global stylesheet cache to fail. These
failures caused content processes to re-load the style sheets,
increasing memory usage.
Differential Revision: https://phabricator.services.mozilla.com/D240928
This disarms a footgun in the FreezableMapping::Freeze API, which was
causing read-only mappings in the global stylesheet cache to fail. These
failures caused content processes to re-load the style sheets,
increasing memory usage.
Differential Revision: https://phabricator.services.mozilla.com/D240928
