1573814 - Use initial `undefined` value for internal slots of Intl objects

Status: RESOLVED FIXED

(Core :: JavaScript: Internationalization API, task)

Description

[André Bargull [:anba]]

Instead of manually setting all Intl objects slots to nullptr resp. NullValue after allocation, we could simply leave them as UndefinedValue, because I don't think there's any added value being able to differentiate between null and undefined when eventually setting the slot value in initializeIntlObject.

Comment 1

[André Bargull [:anba]]

Attachment: Bug 1573814: Use `undefined` for the initial slot values of Intl objects. r=jwalden!

Now that the private slot accessors already handle undefined, we might as
well keep the initial value instead of manually setting the slots to nullptr.

Comment 2

[André Bargull [:anba]]

Try: https://treeherder.mozilla.org/#/jobs?repo=try&revision=562c5a3bd4b4f44c784f409165a8e1a91fe8a0af

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/mozilla-inbound/rev/0eac1a1e4388
Use undefined for the initial slot values of Intl objects. r=jwalden

Comment 4

[Cristian Brindusan [:cbrindusan]]

https://hg.mozilla.org/mozilla-central/rev/0eac1a1e4388