Rikudou_Sage@lemmings.world to Programmer Humor@programming.dev · 14 天前I'm not sure, but it might be something about UUIDslemmings.worldimagemessage-square43fedilinkarrow-up1429arrow-down14
arrow-up1425arrow-down1imageI'm not sure, but it might be something about UUIDslemmings.worldRikudou_Sage@lemmings.world to Programmer Humor@programming.dev · 14 天前message-square43fedilink
minus-squarefour@lemmy.ziplinkfedilinkEnglisharrow-up2arrow-down1·14 天前Shouldnt it be return UUID { uuid: uuid.uuid } ? I think it would make more sense AND more uuid per UUID
minus-squareRikudou_Sage@lemmings.worldOPlinkfedilinkarrow-up3·13 天前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.
minus-squareboonhet@sopuli.xyzlinkfedilinkarrow-up1·13 天前I’m assuming it’s a map/dictionary notation here, rather than a type hint
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