docs: add RFC for opaque generational handles#11
Merged
gituser12981u2 merged 1 commit intoMay 24, 2026
Conversation
gituser12981u2
added
the
documentation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added RFC for opaque handles.
Please put all comments about this RFC here.
For some reason, the last RFC PR broke: #8. I will just paste discussion here since it is already resolved:
Collaborator
alexcu2718
commented
on Mar 27
I do wonder if the singular handle type view maybe a blocker for more eccentric design choices down the road?
One thing we may want to do is use (or create a simple one ourselves?) for a bump allocator, it's piss easy if it's thread local to self write but obviously not suitable. Probably best to investigate this?
(The bump allocator would have to be non-homogenous, pretty simple though.)
*Maybe this comes into mind later down the road, when we're handling game entity objects.
Other than that random discourse, looks really slick. Also love the concept use haha.
Owner
Author
gituser12981u2
commented
on Mar 30
•
Okay, I add allocator input (optional)
gituser12981u2
commented
on Apr 14
I do wonder if the singular handle type view maybe a blocker for more eccentric design choices down the road?
One thing we may want to do is use (or create a simple one ourselves?) for a bump allocator, it's piss easy if it's thread local to self write but obviously not suitable. Probably best to investigate this?
(The bump allocator would have to be non-homogenous, pretty simple though.)
*Maybe this comes into mind later down the road, when we're handling game entity objects.
Other than that random discourse, looks really slick. Also love the concept use haha.
Good idea. I think this should be at the registry level and not the handle level.
gituser12981u2
commented
last month
Implementation discussion moved to #9
alexcu2718
left a comment
lgtm!