Justin Grant
Justin Grant
> > Case 3 is this: > > ```js > > xmas.toLocaleString("ru", {timeZone: zdt.toString(), calendar: zdt.toString()}); > > xmas.toLocaleString("ru", {timeZone: zdt.toString(), calendar: '2020-01-01'}); // assumes the ISO calendar because no...
> Assuming we like to support both case 3 and 4. Could we spec the PR in a way which will only change the step inside toLocaleString but before calling...
> any change inside InitializeDateTimeFormat has the risk to increase unnecessary latency for Date.prototype.toLocaleString unnecessarily. @FrankYFTang If we decide to support cases (3) and (4), then the spec change I...
> Notice your proposed change will also cause a huge compatability issue. Consider the following code: > > ``` > (new Date()).toLocaleString("fr", {calendar: "hello"}); > ``` > > In your...
> It's a strange inconsistency, but I think it's harmless and likely intentional; the Intl.DateTimeFormat simply falls back to the default calendar system for the locale if the provided one...
> See the calling into ToDateTimeOptions for the following https://tc39.es/ecma402/#sup-date.prototype.tolocalestring https://tc39.es/ecma402/#sup-date.prototype.tolocaledatestring https://tc39.es/ecma402/#sup-date.prototype.tolocaletimestring > > Can we make a similar ToTemporalOptions AO for Temporal.*.prototype.toLocaleString that resolve the calendar and timeZone @Ms2ger...
> As I recall, `ToDateTimeOptions` fills in a bunch of defaults that weren't appropriate to create the new Temporal patterns. @Ms2ger `ToDateTimeOptions` is also used by [`Date.p.toLocale*String`](https://tc39.es/ecma402/#sup-date.prototype.tolocalestring) methods. Do those...
I just ran into this problem while trying to set up VSCode debugging of tests run by the the Test262 test harness used to test JS engines like V8. This...
Note that I'd want to remove both the attaching (`"Debugger attached.\n"`) and detaching (`"Waiting for the debugger to disconnect...\n"`) messages.
I agree with @robertbastian that the current state is bad and annoying for both implementers and end-users. FWIW, the current state in ECMAScript is that when the engine doesn't recognize...