News for hackers. Stuff that matters.

A comment on GUIDs Are Not the Only Answer.

Re:GUIDs Are Not the Only Answer by nesarkvechnep on Tuesday January 05, 2021 @05:10PM (#25651890)
"At the very least, identifiers should not be allowed to float freely as strings or integers in order to prevent a class of inconsistency bugs."

Tell that to almost every Typescript developer who uses `number` for identifiers.

[ Parent | on HN ]
Re:GUIDs Are Not the Only Answer by crooked-v on Tuesday January 05, 2021 @05:58PM (#25652404)
Typescript doesn't have functionality for non-equivalent types with identical primitives or interfaces (e.g. you can't have string-equivalent type A ≠ string-equivalent type B), though there's ongoing discussion around adding it (https://github.com/Microsoft/TypeScript/issues/202).
[ Parent | on HN ]
Re:GUIDs Are Not the Only Answer by 0xdeafcafe on Tuesday January 05, 2021 @05:59PM (#25652419)
Arctic take.
[ Parent | on HN ]
Re:GUIDs Are Not the Only Answer by hermanradtke on Tuesday January 05, 2021 @09:35PM (#25654111)
That is why we use things like io-ts. t.Int is a branded type that ensures number is whole and greater than 0.
[ Parent | on HN ]