This is supplementary/separate from the Twitch Streams (see sidebar for links), intended for discussion here on lemmy.
The idea being, now that both twitch streams have read Chapter 4, we can have a discussion here and those from the twitch streams can have a retrospective or re-cap on the topic.
This will be a regular occurrence for each discrete set of topics coming out of The Book as the twitch streams cover them
Ownership and the borrow checker are obviously a fundamental and unique topic to rust, so it’s well worth getting a good grounding in AFAICT.
- Anyone up to trying to summarise or explain ownership/borrow-checker in rust?
- it can be a good exercise to test your understanding and get feedback/clarification from others … as well as probably a good way to teach others
- Any persistent gripes, difficulties or confusions?
- Any of the quizzes from The Book stump you?
- Any hard learnt lessons? Or tried and true tips?
@Jayjader @brokenix @theruran @haitchfive @50htz @vidak all of us to accept the inacceptable with both CPU and compilers.
Because if you step back, ownship should never have been implemented in software code tricks by a compiler, it’s an ugly thing, because insecure. These things should be securely handled in hardware, by the CPU. It’s a design fault.
@Jayjader @brokenix @theruran @haitchfive @50htz @vidak I want you to realize HOW FAR the idea we couldn’t not invent, design, route, produce our own CPU has deeply limited our perception of what computers could alternatively be. This fact has put us into high security conceptual jails for decades. And we have just escaped and are still in a fully readaptation phase with this new freedom acquired.