Issues: tc39/proposal-temporal
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
Label
Projects
Milestones
Assignee
Sort
Issues list
size-suggestio: Suggestions to shrink size of Temporal to address implementer concerns
toStringTag
optimization or removal?
size-suggestion
#2859
opened May 23, 2024 by
justingrant
size-suggestion: do we need Suggestions to shrink size of Temporal to address implementer concerns
toJSON
?
size-suggestion
#2858
opened May 23, 2024 by
justingrant
size-suggestion: consider removing Suggestions to shrink size of Temporal to address implementer concerns
valueOf
?
size-suggestion
#2857
opened May 23, 2024 by
justingrant
size-suggestion: Remove Suggestions to shrink size of Temporal to address implementer concerns
Temporal.Calendar
class and protocol
size-suggestion
#2854
opened May 21, 2024 by
justingrant
size-suggestion: Remove Suggestions to shrink size of Temporal to address implementer concerns
Temporal.TimeZone
class and protocol
size-suggestion
#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 Suggestions to shrink size of Temporal to address implementer concerns
Calendar.p.*FromFields
methods into one
size-suggestion
#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 Suggestions to shrink size of Temporal to address implementer concerns
epoch*
getters and fromEpoch*
methods
size-suggestion
#2849
opened May 20, 2024 by
justingrant
size-suggestions: Consider removing all Suggestions to shrink size of Temporal to address implementer concerns
toXxx
conversion functions
size-suggestion
#2848
opened May 20, 2024 by
justingrant
size-suggestion: Fold some Suggestions to shrink size of Temporal to address implementer concerns
withX()
functions into with()
functions
size-suggestion
#2847
opened May 20, 2024 by
justingrant
size-suggestion: Consider merging Suggestions to shrink size of Temporal to address implementer concerns
Temporal.Now.xISO()
and Temporal.Now.x()
size-suggestion
#2846
opened May 20, 2024 by
justingrant
size-suggestion: Merge Suggestions to shrink size of Temporal to address implementer concerns
since()
and until()
into difference()
size-suggestion
#2845
opened May 20, 2024 by
justingrant
size-suggestion: Consider removing Suggestions to shrink size of Temporal to address implementer concerns
subtract
in favor of add
size-suggestion
#2844
opened May 20, 2024 by
justingrant
is there a specification that Temporal uses to dictate how datetimes are parsed?
meeting-agenda
#2843
opened May 17, 2024 by
BurntSushi
appearing Immutability is not guaranteed by the calling to Calendar during getter calls
feedback
#2842
opened May 17, 2024 by
FrankYFTang
Consistency between string and objects args in plainDate.from()
meeting-agenda
#2840
opened May 15, 2024 by
jasonwilliams
Investigate having read-only properties instead of accessor properties
#2834
opened May 2, 2024 by
ptomato
Remove options parameter from Duration.p.add/subtract
normative
Would be a normative change to the proposal
PlainDateTime::until/since
incorrect results near month boundaries when time-diff has opposite sign
#2820
opened Apr 16, 2024 by
arshaw
Previous Next
ProTip!
no:milestone will show everything without a milestone.