Hi Niko, I'm cleaning up links on http://readrust.net and note this post seems to no longer be on your blog. Is that intentional?
-
-
-
No. I somehow lost the source to this post :( not sure how that happened.
- 2 more replies
New conversation -
-
-
[chanting in distance] Appendix A With Panic=Abort Having Semantic Impact
-
Added a special section just for you =)
- 1 more reply
New conversation -
-
-
May be worth linking to https://github.com/rust-lang/rfcs/pull/1736 … which has some more discussion about exactly this pattern! There's also https://docs.rs/replace_with/ which takes a slightly different approach to take_mut (https://github.com/rust-lang/rfcs/pull/1736#issuecomment-437168646 …).
-
maybe a subject for your next stream? Really love the way you break down complex subjects in Rust.
- 1 more reply
New conversation -
-
-
This is crazy, I *just* ran into this problem, and was going with the `Option` + take route, so your solution of adding a new `Take` struct was perfect timing!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
The idea of &mut into files or shared memory makes me nervous - it's not really unique if other processes can concurrently access it. I suppose it can be made safe with various kinds of locking? (Not really familiar with OS APIs here.)
-
no it's inherently busted, but it's fine because the OS is always more powerful than any language's typesystem. the mmap crate makes it unsafe, but has to otherwise shrug because there's no non-racey way to detect if someone truncated the file you were pointing into
- 1 more reply
New conversation -
-
-
Is there a typo in the Option take example? That `link` param is not used anywhere. Should it be used the line below like `self.chain = Some(Chain::with(link));` or am I missing something here?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.