Patrick Walton e67d63aa79 Refactor the render instance logic in #9903 so that it's easier for other components to adopt. (#10002) ... # Objective Currently, the only way for custom components that participate in rendering to opt into the higher-performance extraction method in #9903 is to implement the `RenderInstances` data structure and the extraction logic manually. This is inconvenient compared to the `ExtractComponent` API. ## Solution This commit creates a new `RenderInstance` trait that mirrors the existing `ExtractComponent` method but uses the higher-performance approach that #9903 uses. Additionally, `RenderInstance` is more flexible than `ExtractComponent`, because it can extract multiple components at once. This makes high-performance rendering components essentially as easy to write as the existing ones based on component extraction. --- ## Changelog ### Added A new `RenderInstance` trait is available mirroring `ExtractComponent`, but using a higher-performance method to extract one or more components to the render world. If you have custom components that rendering takes into account, you may consider migration from `ExtractComponent` to `RenderInstance` for higher performance.		2023-10-08 10:34:44 +00:00
..
src	Refactor the render instance logic in #9903 so that it's easier for other components to adopt. (#10002)	2023-10-08 10:34:44 +00:00
Cargo.toml	Parallelize extract_meshes (#9966)	2023-10-01 09:44:03 +00:00