On Wed, Dec 13, 2023 at 6:10 PM Shu-yu Guo <s...@chromium.org> wrote:

> On Wed, Dec 13, 2023 at 9:03 AM Philip Jägenstedt <foo...@chromium.org>
> wrote:
>
>> LGTM2 for Mike's plan of deprecating for 3 milestones, doing outreach,
>> and then revisiting this thread.
>>
>> If we still know of serious breakage after this, is it an option to
>> simply support both keywords indefinitely, but treat `assert` as legacy?
>> Documentation, linters and autoformatters could all direct developers to
>> `with`, without breaking any existing sites.
>>
>
> Yes, it is an option to support both keywords indefinitely and treat
> `assert` as legacy. TC39 consensus includes `assert` legacy support, on
> account of Chrome having shipped in good faith. We're trying to remove it
> for maximal interop since no other browsers shipped `assert`, but if it's
> not feasible it will not be a willful violation of spec to continue
> shipping it.
>

I see, thank you for clarifying. Looking forward to seeing what the
deprecation and outreach result in.

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAARdPYetzaKxSi_yWTCHd4xJrLh1OAY4YQBdwEN1cHd22kUnoA%40mail.gmail.com.

Reply via email to