-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Consider removing Bevy's "foreach" function systems #42
Comments
fortunately we can have our cake and eat it too thanks to the port to hecs/bevy_ecs. we can have foreach systems and reasonable compile times |
pcwalton
pushed a commit
to pcwalton/bevy
that referenced
this issue
Aug 30, 2021
…ctive Fix for bevyengine#41. support physics_pipeline_active false in all cases.
Closed
CAD97
referenced
this issue
in CAD97/bevy
Nov 17, 2022
tychedelia
pushed a commit
to tychedelia/bevy
that referenced
this issue
Nov 23, 2024
in wasm, errors are printed to the console. This can gives something like: ``` ERROR crates/bevy_render/src/render_resource/pipeline_cache.rs:812 failed to process shader: �[0m�[1m�[38;5;9merror�[0m�[1m: expected ']', found '32'�[0m �[0m�[34m┌─�[0m crates/bevy_pbr/src/render/mesh.wgsl:69:82 �[0m�[34m│�[0m �[0m�[34m69�[0m �[0m�[34m│�[0m var model = bevy_pbr::mesh_bindings::mesh[0u�[0m�[31m32�[0m].model; �[0m�[34m│�[0m �[0m�[31m^^�[0m �[0m�[31mexpected ']'�[0m �[0m�[34m│�[0m �[0m�[34m=�[0m expected ']', found '32' ``` This PR disable term colors in wasm
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From what I can tell, they are incompatible with legion's new lifetimes. Additionally, they add a significant amount of cold compile time (over 20 seconds).
Its a shame because they are so ergonomic:
The text was updated successfully, but these errors were encountered: