Hoist bsn expressions up to reduce ownership / type constraints#23905
Merged
cart merged 1 commit intobevyengine:mainfrom Apr 21, 2026
Merged
Hoist bsn expressions up to reduce ownership / type constraints#23905cart merged 1 commit intobevyengine:mainfrom
cart merged 1 commit intobevyengine:mainfrom
Conversation
viridia
approved these changes
Apr 21, 2026
kfc35
approved these changes
Apr 21, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Objective
bsn!currently embeds expressions directly into the patch closure, which requires moving all of the "expression items" into the closure. This thrusts constraints likeSend + Sync + 'staticon anything used in the expression:Solution
Hoist expression above the closures, evaluate them immediately, and move the results into the closure. This significantly reduces the burden on developers defining scenes.
This now works! No workaround necessary!
Borrowing like this is also allowed because of implicit
into(), which converts the&strintoString, which is then captured in the patch closure:Likewise, patterns like this now work: