Repository navigation
Improve error message "cannot borrow immutable Box content **f as mutable" #51157
Description
Activity
A user on Reddit ran into a similar case but the appropriate binding is marked
mut: https://old.reddit.com/r/rust/comments/9amj6w/hey_rustaceans_got_an_easy_question_ask_here/e50wrlv/I put box in a cell:
let notify: RefCell<Box<dyn FnMut()>> = RefCell::new(Box::new(|| {}));next I borrowed it:
let mut ref_mut = notify.borrow_mut();now for some reason I cannot call it,
ref_mut()gives an error:error[E0596]: cannot borrow immutable `Box` content as mutable --> src/main.rs:6:5 | 6 | ref_mut(); | ^^^^^^^ cannot borrow as mutableAs a workaround I can call it as
(&mut *ref_mut)()but why is this&mut *required?My hypothesis is that the call operator is only attempting immutable deref coercion and requires the deref-reref as a hint to attempt mutable deref coercion instead, but that's a mostly uneducated guess. This seems to be supported by the additional
unused_mutwarning emitted afterwards concerningref_mut:warning: variable does not need to be mutable --> src/main.rs:5:9 | 5 | let mut ref_mut = refcell.borrow_mut(); | ----^^^^^^^ | | | help: remove this `mut` | = note: #[warn(unused_mut)] on by default
The OP's issue is just a piece of bad error reporting in AST borrowck, NLL gives the correct diagnostic:
error[E0596]: cannot borrow `*f` as mutable, as `f` is not declared as mutable --> src/main.rs:4:9 | 2 | fn test(f: Box<FnMut()>) { | - help: consider changing this to be mutable: `mut f` 3 | let _f = move || { 4 | f() | ^ cannot borrow as mutable
The second issue is distinct, at it happens because overloaded call lookup uses an algorithm that is almost, but not quite, the same as method lookup. My proposal for rust-lang/rfcs#2147 would fix that.
Reacted by Jaro Fietz and Esteban Kuber
This error message seems a bit weird, because the problem isn't that box content isn't mutable, but the box itself is immutable. Changing the line 2 to
let mut f: …fixes the issue. Notice that the same error message is shown if we constructfwithin the function.I think the error message should be improved to look similar to the following (not sure on the phrasing of the error itself):