You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Offset grammar will be different between ISO string offsets and offset time zone identifiers after the minutes PR is merged. Does that change any of the simplifications planned here?
Not really; UTCOffset nonterminals are now distinct for a legitimate reason and already incorporate parameterization as appropriate. But I still think some improvements are possible with respect to e.g. |TimeHour|/|TimeMinute|/|TimeFraction|/|TimeSpec| and the Duration productions.
Prefer language like "the first |TemporalDecimalFraction|, if present"
rather than defining several nonterminals such as |TimeFraction|,
|DurationHoursFraction|, etc.
Closes: #2006
@gibson042 pointed out that we don't need to have separate nonterminals such as TimeZoneNumericUTCOffset and TimeZoneUTCOffsetName in order to disambiguate in cases such as #1796. We can refer to things like "the first |FractionalPart|, if present", cf. https://tc39.es/ecma262/multipage/ecmascript-language-statements-and-declarations.html#sec-runtime-semantics-forloopevaluation
The text was updated successfully, but these errors were encountered: