-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Remove Component trait impl from Handle<T> #15716
Copy link
Copy link
Labels
A-AssetsLoad files from disk to use for things like images, models, and soundsLoad files from disk to use for things like images, models, and soundsA-Cross-CuttingImpacts the entire engineImpacts the entire engineC-UsabilityA targeted quality-of-life change that makes Bevy easier to useA targeted quality-of-life change that makes Bevy easier to useX-BlessedHas a large architectural impact or tradeoffs, but the design has been endorsed by decision makersHas a large architectural impact or tradeoffs, but the design has been endorsed by decision makers
Milestone
Description
Metadata
Metadata
Assignees
Labels
A-AssetsLoad files from disk to use for things like images, models, and soundsLoad files from disk to use for things like images, models, and soundsA-Cross-CuttingImpacts the entire engineImpacts the entire engineC-UsabilityA targeted quality-of-life change that makes Bevy easier to useA targeted quality-of-life change that makes Bevy easier to useX-BlessedHas a large architectural impact or tradeoffs, but the design has been endorsed by decision makersHas a large architectural impact or tradeoffs, but the design has been endorsed by decision makers
Objective
Remove the
Componenttrait implementation fromHandle<T>as its usage is now considered an anti-pattern.The move to required components has notably made porting error prone both internally and for the code of early adopters. Due a lack of errors on the usage of high-profile but now no longer relevant
Handlecomponents likeHandle<Mesh>andHandle<StandardMaterial>.