|
|
|
|
|
|
by jkbyc
4685 days ago
|
|
|
I agree, the actual content doesn't match the introduction so well. I've been looking into Rust during the past few days and I must say I got stuck on the memory model - all the different pointers and their interaction with ownership and mutability, closures capturing their environment (variables outside the closure in the scope where the closure is defined), reference binding, and then things like std::Cell which on the one hand seems to be an alternative to std::Option but on the other hand it's using some unsafe operations in its implementation to change mutability or something... It's quite confusing and it stopped me from writing a simple example application I wanted to write because I wanted to understand what's going on a bit better first. |
|
|
@ is going to sink into the library and will be deemphasized in the language to help with this. That leaves only ~ (pointers) and & (references).
> closures capturing their environment (variables outside the closure in the scope where the closure is defined)
Right, this is one of the difficult pieces. This is going away as well in favor of Java-like Runnables to make the variable capture easier to understand (with macro sugar to make them just as convenient as closures). The closures that remain will work just like the closures you know from other languages regarding variable capture, and the Rust-specific stuff regarding variable capture will be gone.
> std::Cell
Yeah, this needs to be better documented. Part of the problem is that we haven't totally nailed down what Cell will be used for yet.