Skip to content

Issues: tc39/proposal-temporal

Final normative spec text plan
#2628 opened Jul 13, 2023 by ptomato
Open 1
Possible to pare down code size?
#2786 opened Feb 23, 2024 by syg
Open 12
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Author
Filter by author
Label
Filter by label
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Milestones
Filter by milestone
Assignee
Filter by who’s assigned
Sort

Issues list

size-suggestio: toStringTag optimization or removal? size-suggestion Suggestions to shrink size of Temporal to address implementer concerns
#2859 opened May 23, 2024 by justingrant
size-suggestion: do we need toJSON? size-suggestion Suggestions to shrink size of Temporal to address implementer concerns
#2858 opened May 23, 2024 by justingrant
size-suggestion: consider removing valueOf ? size-suggestion Suggestions to shrink size of Temporal to address implementer concerns
#2857 opened May 23, 2024 by justingrant
Options object consumption is observably different in internal branches behavior Relating to behavior defined in the proposal bug normative Would be a normative change to the proposal spec-text Specification text involved
#2855 opened May 21, 2024 by gibson042
size-suggestion: Remove Temporal.Calendar class and protocol size-suggestion Suggestions to shrink size of Temporal to address implementer concerns
#2854 opened May 21, 2024 by justingrant
size-suggestion: Remove Temporal.TimeZone class and protocol size-suggestion Suggestions to shrink size of Temporal to address implementer concerns
#2853 opened May 21, 2024 by justingrant
size-suggestion: Should custom calendars eagerly calculate all fields at construction time? size-suggestion Suggestions to shrink size of Temporal to address implementer concerns
#2852 opened May 20, 2024 by justingrant
size-suggestion: Consider merging three Calendar.p.*FromFields methods into one size-suggestion Suggestions to shrink size of Temporal to address implementer concerns
#2851 opened May 20, 2024 by justingrant
size-suggestion: Consider merging getNextTransition/getPreviousTransition into one with a direction option size-suggestion Suggestions to shrink size of Temporal to address implementer concerns
#2850 opened May 20, 2024 by justingrant
size-suggestion: Consider removing some epoch* getters and fromEpoch* methods size-suggestion Suggestions to shrink size of Temporal to address implementer concerns
#2849 opened May 20, 2024 by justingrant
size-suggestions: Consider removing all toXxx conversion functions size-suggestion Suggestions to shrink size of Temporal to address implementer concerns
#2848 opened May 20, 2024 by justingrant
size-suggestion: Fold some withX() functions into with() functions size-suggestion Suggestions to shrink size of Temporal to address implementer concerns
#2847 opened May 20, 2024 by justingrant
size-suggestion: Consider merging Temporal.Now.xISO() and Temporal.Now.x() size-suggestion Suggestions to shrink size of Temporal to address implementer concerns
#2846 opened May 20, 2024 by justingrant
size-suggestion: Merge since() and until() into difference() size-suggestion Suggestions to shrink size of Temporal to address implementer concerns
#2845 opened May 20, 2024 by justingrant
size-suggestion: Consider removing subtract in favor of add size-suggestion Suggestions to shrink size of Temporal to address implementer concerns
#2844 opened May 20, 2024 by justingrant
Remove options parameter from Duration.p.add/subtract normative Would be a normative change to the proposal
#2825 opened Apr 18, 2024 by ptomato Stage "3.5"
ProTip! no:milestone will show everything without a milestone.