-
-
Notifications
You must be signed in to change notification settings - Fork 4k
Improve spec_v2
patterns
#20114
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
Open
ecoskey
wants to merge
17
commits into
bevyengine:main
Choose a base branch
from
ecoskey:nuke_get_base_descriptor
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Improve spec_v2
patterns
#20114
Changes from all commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
0d9f1c8
nuke most of stuff
ecoskey 2db1ef9
edit migration guide with new patterns
ecoskey c1c4da8
remove unused code
ecoskey e0f7036
fix ci
ecoskey f893fd5
clarification
ecoskey eb53ccc
more clarification
ecoskey 913f53b
fix example
ecoskey 74d91e0
fix ci
ecoskey 33fcee8
phrasing
ecoskey f1ccd01
nuke user specializers
ecoskey 8fd6918
Merge branch 'main' into nuke_get_base_descriptor
ecoskey d787a0f
add empty bind group layout
ecoskey f995079
add set_layout
ecoskey 95f98e4
oops
ecoskey 630da13
Merge branch 'main' into nuke_get_base_descriptor
ecoskey 879b362
re-add set_target
ecoskey 76ed8fd
fix migration guide
ecoskey File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
Hmm, so we now use an empty layout in a few places post wgpu 25, but I'm a little wary about this. I guess the set_at api is nicer than just doing a
push
like we do in some places, but I'm not sure I understand why it should ever be necessary to implicitly fill in the holes in a layout?Uh oh!
There was an error while loading. Please reload this page.
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.
Only with the assumption that it'll be properly filled in by other logic, like by composing specializers.
There's probably a better solution than
filling_set_at
, but since specializers can't really rely on their input having a certain shape (like what the current length of the vec is) bothpush
and direct indexing cause problems without bounds checks or padding.