bytevectors containing both references and data?
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 12/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- compilers
Research direction
The issue asks whether a bytevector can mark a region as holding GC-tracked pointers, using bytevector-reference-set! alongside the bytevector-ieee-double-native-set! and bytevector-s64-native-set! accessors. Start by reading how reference bytevectors are represented and traced by the collector, then check whether a mixed layout is already possible. Done means a written design decision or maintainer answer on mixed-region support, not a patch.
Written by the indexing model from the issue text.
Description
It's my understanding that with reference bytevectors, we can treat them as arrays of pointers to scheme objects such that when one of those scheme objects are moved, the pointers in the reference bytevector are updated. Is it possible to mark a specific region in a bytevector as a pointer?
For example:
(define obj-parent (make-bytevector 16))
(define obj-child (make-bytevector 8))
(bytevector-reference-set! obj-parent 0 obj-child)
(bytevector-ieee-double-native-set! obj-parent 8 3.14)
(bytevector-s64-native-set! obj-child 0 42)
Real world use case is SDL_GPUVertexInputState.
It's not really a problem but it would be convenient if the GC could help manage these structures.
- Dominant language
- Scheme
- Stars
- 7.4k
- Forks
- 1k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 19
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from cisco/ChezScheme
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
cisco/ChezScheme#1110 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
cisco/ChezScheme#1111 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
cisco/ChezScheme#1078 · 1 comment ·
Maintainers usually reply within 1 day
-
RFC: solution to clangd not finding "scheme.h"Possibly taken @reginaldalfret claimed this 20 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
cisco/ChezScheme#1073 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
cisco/ChezScheme#1063 ·
Maintainers usually reply within 1 day
All issues in cisco/ChezScheme
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 82/100
supercollider/supercollider#7872 · 1 comment ·
Maintainers usually reply within 1 day
-
bug I/O low priority semantics
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
pocket-stack/pocketjs#729 ·
-
[BUG]: C# programs with top-level statements fail to compilePossibly taken @AsyncNigam claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
compiler-explorer/compiler-explorer#9625 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
baseballyama/rsvelte#5086 ·
Maintainers usually reply within 1 day