max-mapper / max-mapper/bytewiser
Desired explanation for bonus challenge in final problem?
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 210
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
I'd love to see some definitive explanation for the bonus challenge presented in the final problem.
We know that a Uint16Array typed array represents an array of unsigned 16-bit integers and that the representation changes (viz., in the "offsets", I think) after 4294967295.
4294967294 '{"0":65534,"1":65535,"BYTES_PER_ELEMENT":2,"buffer":{"0":254,"1":255,"2":255,"3":255,"byteLength":4},"length":2,"byteOffset":0,"byteLength":4}'
4294967295 '{"0":65535,"1":65535,"BYTES_PER_ELEMENT":2,"buffer":{"0":255,"1":255,"2":255,"3":255,"byteLength":4},"length":2,"byteOffset":0,"byteLength":4}'
4294967296 '{"0":0,"1":0,"BYTES_PER_ELEMENT":2,"buffer":{"0":0,"1":0,"2":0,"3":0,"byteLength":4},"length":2,"byteOffset":0,"byteLength":4}'
Contributor guide
No contributing guide indexed for this repository
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 with problems/array_buffers/problem.txt, especially the bonus challenge at lines 13-14, and compare it with the reported Uint16Array outputs around 4294967295. Explain why the representation changes at 4294967296 and document the result in the workshop material; the issue is complete when the bonus challenge has a definitive explanation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100