Hi all!

What?

I will be holding the fourth of the secondary slot/sessions for the Reading Club, also on “The Book” (“The Rust Programming Language”). We are using the Brown University online edition (that has some added quizzes & interactive elements). This week, we will be starting chapter 4: “Understanding Ownership”.

Previous session details and recording can be found in the following lemmy post: https://jlai.lu/post/5278834

Why?

This slot is primarily to offer an alternative to the main reading club’s streams that caters to a different set of time zone preferences and/or availability.

(also, obviously, to follow up on the previous session)

When ?

Currently, I intend to start at 18:00 UTC+1 (aka 6pm Central European Time) on Monday (2023-03-25). If you were present for a previous session, then basically the same time as that one was.

Please comment if you are interested in joining because you can’t make the main sessions but would prefer a different start time (and include a time that works best for you in your comment!). Caveat: I live in central/western Europe; I can’t myself cater to absolutely any preference.

How ?

The basic format is: I will be sharing my computer screen and voice through an internet live stream (hosted at https://www.twitch.tv/jayjader for now). The stream will simultaneously be recorded locally and uploaded afterwards to youtube (also, for now). Edit: the recording can be found at the following link: https://youtu.be/YmMreNK3fcw.

I will have on-screen:

the BU online version of The Book
a terminal session with the necessary tooling installed (notably rustup and through it cargo & “friends”)
some form of visual aid (currently a digital whiteboard using www.excalidraw.com)
the live stream’s chat

I will steadily progress through the chapter, both reading aloud the literal chapter text and commenting occasionally on it. I will also perform any code writing and/or terminal commands as the text instructs us to.

People who either tune in to the live stream or watch/listen to the recording are encouraged to follow along with their own copy of the book.

I try to address any comments from live viewers in the twitch chat as soon as I am aware of them. If someone is having trouble understanding something, I will stop and try to help them get past it.

The interactive quizzes have started getting more interesting! Unfortunately, we’re still on a decent delay from when I’m speaking to when I see people’s comments appear in chat, so we will most likely continue to work through them in a more disjointed manner than the rest of the material.

Who ?

You! (if you’re interested). And, of course, me.

Welcome

A collaborative space for people to work together on learning Rust, learning about the Lemmy code base, discussing whatever confusions or difficulties we’re having in these endeavours, and solving problems, including, hopefully, some contributions back to the Lemmy code base.

Rules TL;DR: Be nice, constructive, and focus on learning and working together on understanding Rust and Lemmy.

Policies and Purposes

This is a place to learn and work together.

Questions and curiosity is welcome and encouraged.

This isn’t a technical support community. Those with technical knowledge and experienced aren’t obliged to help, though such is very welcome. This is closer to a library of study groups than stackoverflow. Though, forming a repository of useful information would be a good side effect.

This isn’t an issue tracker for Lemmy (or Rust) or a place for suggestions. Instead, it’s where the nature of an issue, what possible solutions might exist and how they could be or were implemented can be discussed, or, where the means by which a particular suggestion could be implemented is discussed.

See also:

Rules

Lemmy.ml rule 2 applies strongly: “Be respectful, even when disagreeing. Everyone should feel welcome” (see Dessalines’s post). This is a constructive space.

Don’t demean, intimidate or do anything that isn’t constructive and encouraging to anyone trying to learn or understand. People should feel free to ask questions, be curious, and fill their gaps knowledge and understanding.

Posts and comments should be (more or less) within scope (on which see Policies and Purposes above).

See the Lemmy Code of Conduct

Where applicable, rules should be interpreted in light of the Policies and Purposes.

Relevant links and Related Communities

Thumbnail and banner generated by ChatGPT.

Jayjader@jlai.luOPM English

1·

3 months ago

We got all the way through section 4.1, and the first half of section 4.2 (the last thing we covered during the session was what The Book calls the “Pointer Safety Principle: data should never be aliased and mutated at the same time.”

We’ll pick up from that point next week/session.