Intl: Consider deprecating Intl.v8BreakIterator

[jasnell]

@littledan has put forward a TC-39 proposal to introduce Intl.Segmenter as a standardized replacement for the V8 specific Intl.v8BreakIterator.

Currently in Node.js, Intl.v8BreakIterator only works if the full-icu data is being used. Attempting to create an instance of Intl.v8BreakIterator with the default small-icu with throw. That said, given the desire to replace it with a standardized alternative we should consider emitting a runtime deprecation warning when it is used.

/cc @srl295 @caridy @nodejs/ctc @nodejs/tc39

[srl295]

Makes sense… is there a need to deprecate something that's really v8 internal? So I'm +0.0 on this subject to rounding err!

[littledan]

I hope no one new starts using the deprecated API, but it's currently exposed to some Node users. I'd support a runtime deprecation warning but would be even happier if it were just deleted. I hope to remove it entirely from a future version of V8.

[srl295]

Deletion makes sense too. I'm +1 on principle just not sure about policy details.

Enviado desde nuestro iPhone.

El oct. 1, 2016, a las 12:35 PM, littledan notifications@github.com escribió:

I hope no one new starts using the deprecated API, but it's currently exposed to some Node users. I'd support a runtime deprecation warning but would be even happier if it were just deleted. I hope to remove it entirely from a future version of V8.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[jasnell]

We have to deprecate first in one major before we can remove in the next.

On Saturday, October 1, 2016, Steven R. Loomis notifications@github.com
wrote:

Deletion makes sense too. I'm +1 on principle just not sure about policy
details.

Enviado desde nuestro iPhone.

El oct. 1, 2016, a las 12:35 PM, littledan <notifications@github.com
javascript:_e(%7B%7D,'cvml','notifications@github.com');> escribió:

I hope no one new starts using the deprecated API, but it's currently
exposed to some Node users. I'd support a runtime deprecation warning but
would be even happier if it were just deleted. I hope to remove it entirely
from a future version of V8.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#8865 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAa2eeHBPMPPYSlP9a66MhHwOGTR76LPks5qvs4KgaJpZM4KLXGH
.

[srl295]

Makes sense

[caridy]

@srl295 I thought we had discussed this in the past, and agreed on throwing an error, at least that was my understanding. Anyhow, let's try to take action asap, to prevent a bigger problem later on.

[Fishrock123]

If there is a chance this will be removed before the next major we should deprecate in v7.

[jasnell]

I'm thinking we probably should. I'm not able to add the ctc-agenda label
at the moment. We would need ctc ok to land it in v7.

On Monday, October 3, 2016, Jeremiah Senkpiel notifications@github.com
wrote:

If there is a chance this will be removed before the next major we should
deprecate in v7.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#8865 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAa2ef5BMHzosnWYo6fyrDTuOeNRWNSuks5qwQgwgaJpZM4KLXGH
.

[targos]

Here is a PR adding the deprecation warning: #8908