#'&World conflicts with a previous mutable system parameter. Allowing this would break Rust's

1 messages · Page 1 of 1 (latest)

ashen olive
ruby cobalt
#

The problem is that stuff like ResMut, &mut MyComponent, etc. require mutable access to the world. So it would be unsound and break Rust’s borrow rules to have both a mutable access and immutable one to the world

faint kraken
#

And once you have &mut World, resource_scope can be really handy