-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[Merged by Bors] - Add ReplaceChildren and ClearChildren EntityCommands #6035
Closed
Closed
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
0d6b8a9
add ClearChildren and ReplaceChildren EntityCommand
ld000 81c3e9e
clear_children not clone children, use remove instead
3bfe1c4
format code
aa7179e
Merge remote-tracking branch 'origin/main' into feature/add-clear-rep…
df5ebf7
resolve conversation
ld000 e91e911
Merge branch 'main' into feature/add-clear-replace-command
ld000 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 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
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.
It's generally better to use an iterator type instead of forcing someone to use a
slice
. Since it's not always guaranteed that the children entities will be in an array-like container.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.
Nice advice. But this change will get the error: the trait
smallvec::Array
is not implemented forimpl IntoIterator<Item = Entity>
, doessmallvec::Array
need to imply this trait?Also, does
push_children(&mut self, children: &[Entity])
,insert_children(&mut self, index: usize, children: &[Entity])
andremove_children(&mut self, children: &[Entity])
functions also need to change thechildren
parameter type toimpl IntoIterator<Item = Entity>
?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 believe you can use the
FromIterator
implementation onSmallVec
(SmallVec::from_iter
) instead ofSmallVec::from
.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.
It's probably better to handle this in a separate PR that updates all the methods to take
IntoIterator
.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'll open a separate PR for this!