-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Type-erased Specializers #20391
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Type-erased Specializers #20391
Conversation
d53dcb5
to
ddf6e47
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs a migration guide :)
It looks like your PR is a breaking change, but you didn't provide a migration guide. Please review the instructions for writing migration guides, then expand or revise the content in the migration guides directory to reflect your changes. |
This comment was marked as resolved.
This comment was marked as resolved.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Migration guide looks fine, but I don't have the rendering chops to review this further :)
Add type-erased wrappers around
Specializer
andSpecializerKey
Currently, type-erased materials have their key type and key getter located in
AsBindGroup
, and theirspecialize
fn located inMaterial
. This is mostly an experiment, but I think erased specializers might be a good way to wrap all that logic up nicely.Currently there's more boxing than there should be, I'll probably switch to some form of
bytemuck
orSmallBox
laterblocked on #20348