RustCurious 1: Why Rust is Safe #6953
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi, this video is an introduction to borrowed references and ownership that I hope you'll find sufficiently novel. It avoids using any Rust syntax, instead walking through the invention of a thought-experiment language based on C. It's based on Aria Desire's way of explaining ownership. The basic structure is:
File
example: It's still possible to cause use-after-close on a file :(write
function consumes the file :(Array
example -push
works great, but no way to get a pointer to an element in-place :(get
function :)