Skip to content

docs: add RFC for opaque generational handles#8

Merged
gituser12981u2 merged 6 commits into
alex_stufffrom
docs/rfc-0001-opaque-generational-handles
May 7, 2026
Merged

docs: add RFC for opaque generational handles#8
gituser12981u2 merged 6 commits into
alex_stufffrom
docs/rfc-0001-opaque-generational-handles

Conversation

@gituser12981u2
Copy link
Copy Markdown
Owner

Added RFC for opaque handles.

Please put all comments about this RFC here.

@gituser12981u2 gituser12981u2 self-assigned this Mar 22, 2026
@gituser12981u2 gituser12981u2 added the documentation Improvements or additions to documentation label Mar 22, 2026
@alexcu2718
Copy link
Copy Markdown
Collaborator

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.

@gituser12981u2
Copy link
Copy Markdown
Owner Author

gituser12981u2 commented Mar 30, 2026

Okay, I add allocator input (optional)

Comment thread src/backend/vulkan/instance/debug_messenger.cpp Outdated
Comment thread src/backend/vulkan/instance/instance.cpp Outdated
Comment thread src/backend/vulkan/instance/instance.cpp
Comment thread src/backend/vulkan/instance/instance.cpp
Comment thread src/backend/vulkan/instance/instance_bundle.cpp Outdated
Comment thread src/backend/vulkan/instance/instance_bundle.cpp Outdated
Comment thread src/backend/vulkan/presentation/swapchain.cpp Outdated
Comment thread src/platform/window/glfw_window.cpp
Comment thread .clang-tidy
@gituser12981u2
Copy link
Copy Markdown
Owner Author

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
Copy link
Copy Markdown
Owner Author

Implementation discussion moved to #9

Copy link
Copy Markdown
Collaborator

@alexcu2718 alexcu2718 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm!

@gituser12981u2 gituser12981u2 merged commit e6b7edd into alex_stuff May 7, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants