The feeling you get when searching your codebase for references to your “uid” variable but this cheeky boy keeps popping up.
n, n, n, nn, nnnnnnnnnnnnnnnnnnn, n, nn, n, n,n …
Why I love the Into trait in rust
Picture isn’t loading for me?
Thanks, kind stranger. And wow, I haven’t seen that much UUID since I coded for Second Life.
are you from the UK by any chance
Yes
same - i think it’s because the image is blocked in the UK because of the online safety act. Try using a VPN and see if that helps
Actually I’ve since learned that it’s because imgur was collecting kids’ private data, and decided to block the UK rather than stop.
omfg of course, classic $BIG_CORP$ stuff
Shouldnt it be
return UUID { uuid: uuid.uuid }?I think it would make more sense AND more uuid per UUID
The first UUID is a local type, the second is the name of an embedded struct, the third is the name of the variable.
The struct looks something like this (writing this on my phone)
type UUID struct { uuid.UUID }
So, basically, this is a custom wrapper for a third party UUID implementation.
Ahh, that makes sense then
I’m assuming it’s a map/dictionary notation here, rather than a type hint
When you get a new boss at Twitter who ranks people by lines of code written
i’ve now read UUID so many times i’m starting to think it’s some kind of sex disease
That must one awkward conversation… “Can you explain where did you get the uuid from?”
i told you last logic loop NO
UwUID
My coworkers also introduce needless additions to the call stack
I’ve read so many tutorials like this. func Func Myfunc()
If you write textbooks like this you and your family should be boiled in sewage.
Semantic satiation. Or whatever it’s called, i think ive officially lost it after reading this
I read the code like half a dozen times and my brain hurts.
Plot twist: it returns the bios serial.
If this was C:
#define uuID func #define uuiD return#define satan fubarx
:3
Where did i put that Spiderman x3 pointing meme?
