-
Notifications
You must be signed in to change notification settings - Fork 45
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
Naga 0.20 #87
Naga 0.20 #87
Conversation
Discussed this with robtfm on discord, and there seems to be 2 ways forwards for supporting pipeline overridable constants.
|
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.
just a couple of minor nits on derive.
i also wanted to keep the prune support so i've done that. i made a pr to your branch with the comment changes and the prune code
0.20 prune
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.
also note - the function to map pipeline const names is already there - Composer::decorated_name
does the job.
thanks very much for taking this on.
🤦 |
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.
Haven't actually tested subgroups/pipeline overrides, but approving it conditional on it working. I'll have to hook this up to bevy and try it out when I'm next free.
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.
I haven't seen anything obviously wrong in the code and I tested it with almost all 2d and 3d examples with no issues. So LGTM
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.
lgtm
i hope the wgpu api will change to put subgroup stages into the capabilities struct in future.
Pipeline override constants will be fully implemented in a followup PR.
They're theoretically working, but they need tests and also need a function to map the unmangled names to the mangled names.
Otherwise this appears to work. I've tested it with bevy and everything seemed to work.