@themovercell.bsky.social
Reposted
*gets woken up by interrupt* eeeughg...aehhgj.......gg..
January 15, 2026 at 8:18 PM
*gets woken up by interrupt* eeeughg...aehhgj.......gg..
Reposted
You guys are so fucking stupid. When I was in high school 15 years ago, I didn't read any of the books my teachers assigned me either. I was busy reading better books. They were already assigning excerpts of plays instead of reading it all. Kids still read books they just have better taste than you.
December 12, 2025 at 1:20 PM
You guys are so fucking stupid. When I was in high school 15 years ago, I didn't read any of the books my teachers assigned me either. I was busy reading better books. They were already assigning excerpts of plays instead of reading it all. Kids still read books they just have better taste than you.
Reposted
what I couldn't give for updated book lists. bonus points for including books that haven't been adapted to film lol.
December 12, 2025 at 1:31 PM
what I couldn't give for updated book lists. bonus points for including books that haven't been adapted to film lol.
Whoops I didn't notice that date, sorry.
December 13, 2025 at 12:59 PM
Whoops I didn't notice that date, sorry.
"because it has all the same issues"
It does not, the problem demonstrated in the post is not applicable to c++ since the function should just accept an std::span(an array pointer+size, also can be implicitly converted to from std::array) and the problem would be gone.
It does not, the problem demonstrated in the post is not applicable to c++ since the function should just accept an std::span(an array pointer+size, also can be implicitly converted to from std::array) and the problem would be gone.
December 12, 2025 at 10:53 AM
"because it has all the same issues"
It does not, the problem demonstrated in the post is not applicable to c++ since the function should just accept an std::span(an array pointer+size, also can be implicitly converted to from std::array) and the problem would be gone.
It does not, the problem demonstrated in the post is not applicable to c++ since the function should just accept an std::span(an array pointer+size, also can be implicitly converted to from std::array) and the problem would be gone.
That's why you use std::unique_ptr
December 12, 2025 at 10:49 AM
That's why you use std::unique_ptr
Reposted
you're working with some very old material if it's still recommending raw pointers or C arrays en.cppreference.com/w/cpp/contai...
std::array - cppreference.com
en.cppreference.com
November 18, 2025 at 3:01 PM
you're working with some very old material if it's still recommending raw pointers or C arrays en.cppreference.com/w/cpp/contai...
Reposted
I used to be an assembler like you. Then I took a pointer to the knee.
November 19, 2025 at 5:27 PM
I used to be an assembler like you. Then I took a pointer to the knee.
Reposted
There are two ways to use C++
1) It's a new language that happens to be backwards-compatible with C.
2) It's C with a whole bunch of new features.
If you're using arrays or pointers instead of templates, you're doing (2). If your name isn't Linus Torvalds, you're not smart enough to do it safely.
1) It's a new language that happens to be backwards-compatible with C.
2) It's C with a whole bunch of new features.
If you're using arrays or pointers instead of templates, you're doing (2). If your name isn't Linus Torvalds, you're not smart enough to do it safely.
November 18, 2025 at 3:00 PM
There are two ways to use C++
1) It's a new language that happens to be backwards-compatible with C.
2) It's C with a whole bunch of new features.
If you're using arrays or pointers instead of templates, you're doing (2). If your name isn't Linus Torvalds, you're not smart enough to do it safely.
1) It's a new language that happens to be backwards-compatible with C.
2) It's C with a whole bunch of new features.
If you're using arrays or pointers instead of templates, you're doing (2). If your name isn't Linus Torvalds, you're not smart enough to do it safely.