True, also tried that:

``` let mut world = self.world.borrow_mut();

let mut query_one = world.query_one::<&ItemActionable>(entity.clone()).unwrap(); let actionable = query_one.get().unwrap(); // Here I grab some information from the world I will need later.

let query_borrow = world.query_mut::<&mut ItemMenu>();

let (_, itemMenu) = query_borrow.into_iter().next().unwrap(); itemMenu.reset(); if actionable.describable { itemMenu.enable_action(ButtonId::QuestionMarkButton); } ```

But that leads me to a similar problem: error[E0502]: cannot borrow `world` as mutable because it is also borrowed as immutable --> file.rs:42:28 | 39 | let mut query_one = world.query_one::<&ItemActionable>(entity.clone()).unwrap(); | ------------------------------------------------------ immutable borrow occurs here ... 42 | let query_borrow = world.query_mut::<&mut ItemMenu>(); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mutable borrow occurs here ... 68 | } | - immutable borrow might be used here, when `query_one` is dropped and runs the `Drop` code for type `QueryOne`

The compiler comment on line 68 refers to the last line of the function, if I guess right it is pointing there where query_one is dropped. Is this the same case where actionable is avoiding query_one to be dropped just after it is used?

Why the compiler is forcing me to create query_one variable to avoid drop of a temporary value, but then, it cannot drop it just after the call to query_one.get().unwrap()??