←back to thread

Shared_ptr<T>: the (not always) atomic reference counted smart pointer (2019)

(snf.github.io)
51 points klaussilveira | 1 comments | 27 Aug 25 14:34 UTC | HN request time: 0s | source
Show context
ptspts ◴[31 Aug 25 12:03 UTC] No.45082527[source]▶
The correct spelling is in lowercase: shared_ptr<T> . The title of the article is correct, the title of the HN post is incorrect.
replies(2): >>45082838 #>>45082918 #
tialaramex ◴[31 Aug 25 13:02 UTC] No.45082838[source]▶
In hindsight this convention seems weird to me by the way. I didn't question it for the decades I was paid money to write C, but after adopting Rust it jumped out more that it's weird how monocase the C and C++ standard libraries are.

Maybe there's a reason I'd never run into, but this seems like a missed opportunity. Even if I have no idea what Goose is, I can see it's a type, that seems like a win.

replies(1): >>45085062 #
1. recursivecaveat ◴[31 Aug 25 17:33 UTC] No.45085062[source]▶
Yeah I don't know why so many C programmers ended up on a convention where case is entirely unused. I wonder if it's some ancient compatability thing that they have just been keeping self-consistent with forever. To me not using case is like designing a road map in black-and-white just because you didn't have any ideas for what colors should represent.