Add the API as a Intl.prototype function instead.

[FrankYFTang]

I suggest we add this functionality as a function in Intl instead of adding a new LocaleMatcher object.

Instead of

Intl.LocaleMatcher.match(["fr-XX", "en"], ["fr", "en"], "en"); // 'fr'

How about

Intl.matchLocale(["fr-XX", "en"], ["fr", "en"], "en"); // 'fr'

[longlho]

yeah I'm open to that as well. Although @sffc brought up a point where certain matching algorithm might require additional CLDR data so I can also see something like:

new Intl.LocaleMatcher({ algorithm: 'lookup' }) // This is the RFC4647 one that requires no addl data
(await new Intl.LocaleMatcher({ algorithm: 'unicode' })).match() // This is UTS35 LanguageMatching which needs maximize/minimize

Reference: tc39/ecma402#210