He is back! Nice to see you also switched to english. And that you work with rust ;-)

Thank you for the clear explanations. What would be a use case for using Refcell? Using a Mutex for a multi-threaded application can be understoof easily, but I have a hard time to grasp when to use refcell instead of having a mutable reference.

@FloWoelki

3 ай бұрын

thank you for the question. i think a good use case for `RefCell` would be when you want to modify data with a shared struct. for instance, if we want to clone a struct but we want to keep track of the reference and whenever we manipulate something from the cloned struct, it will update the original one. maybe this code helps to better understand the use case: ``` struct Counter { value: RefCell, } fn main() { let counter = Rc::new(Counter { value: RefCell::new(0) }); let counter_clone = counter.clone(); // We can modify the counter even though it's shared: *counter_clone.value.borrow_mut() += 1; println!("Counter value: {}", counter.value.borrow()); } ```

What plugin makes the errors appear right at the end of the line like that?

@xyangst

4 ай бұрын

Error lens

@xyangst

4 ай бұрын

Nvm its nvim umm works out of the box i think

@FloWoelki

4 ай бұрын

exactly. you could try "Error lens" for vs code. for nvim, i personally use zero-lsp which also shows me the error inline.

@jay.rhoden

4 ай бұрын

@@xyangst Hmmm, I use neovim and it doesn't do that for me with lsp turned on.

@FloWoelki

4 ай бұрын

you also need to enable the inline diagnostics (ref to this link: neovim.io/doc/user/diagnostic.html#vim.diagnostic.config()). hope that helps :)

Thank you for your video! but I don't completely understand by you println before v.push() then you expect to print new result included value from v.push(). how about this code? fn c

@FloWoelki

3 ай бұрын

awesome, that you've liked this video :) i am not 100% sure what you mean with your question, but i'll try to answer it through reading the code and result :D the reason, why things are not mutate correctly is because we are cloning the vector with all its elements into a new memory address. so we basically do a copy paste and only mutate the vector inside of the closure.