TypedArray interface
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 3.7k
- Forks
- 177
- PR merge metrics
- No merged PRs in 30d
Description
Would adding a 32-bit date representation for Temporal.Date (eg. days since 1970-01-01 like Apache Arrow does) be in scope of this spec? Similarly 64-bit datetime for Temporal.DateTime could work.
Maybe this would help WASM interoperability too.
I know anybody can map the Date and DateTime to 32 and 64bit numbers resp., but adding the reference values would make sense. Adding a few extra methods to a Uint32Array/Float64Array subclass would make the developer experience better, too.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the proposed Temporal.Date and Temporal.DateTime representations against the Apache Arrow date32 reference linked in the issue, then consider the suggested Uint32Array/Float64Array subclass methods and possible WASM interoperability. Done would require a clear specification decision on whether these representations and interfaces belong in Temporal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, wasm
- Domain
- api, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100