Re: [webkit-dev] Proposal: Removing ENABLE(INTL)

[Leo Balter]

As a representative from TC39, I celebrate this decision and I hope to see
Intl is progressively implemented as the EcmaScript
features.

Please, let me know if you want feedback from test262 perspective, this
might support the information on impl maturity.

On Sat, May 19, 2018 at 7:12 AM Yusuke SUZUKI  wrote:

> Hi WebKittens,
>
> I would like to remove ENABLE(INTL) compile time flag and always enable
> INTL.
> This is ECMAScript Intl (i18n) feature. This feature depends on ICU.
> But right now, even JSC (and WTF) always require ICU. Even if we disable
> ENABLE(INTL), we still require ICU.
>
> New INTL features are gurded separately with the compile flags (since some
> new features require new ICU). So, removing ENABLE(INTL) just enables Intl
> basic features, which are shipped more than 1 year ago and it is quite
> mature.
>
> Best regards,
> Yusuke Suzuki
> --
> Regards,
> Yusuke Suzuki
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev
>
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

[webkit-dev] Proposal: Removing ENABLE(INTL)

[Yusuke SUZUKI]

Hi WebKittens,

I would like to remove ENABLE(INTL) compile time flag and always enable
INTL.
This is ECMAScript Intl (i18n) feature. This feature depends on ICU.
But right now, even JSC (and WTF) always require ICU. Even if we disable
ENABLE(INTL), we still require ICU.

New INTL features are gurded separately with the compile flags (since some
new features require new ICU). So, removing ENABLE(INTL) just enables Intl
basic features, which are shipped more than 1 year ago and it is quite
mature.

Best regards,
Yusuke Suzuki
-- 
Regards,
Yusuke Suzuki
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev