[HN Gopher] Sets, types and type checking
       ___________________________________________________________________
        
       Sets, types and type checking
        
       Author : kaleidawave
       Score  : 38 points
       Date   : 2024-10-30 18:53 UTC (1 days ago)
        
 (HTM) web link (kaleidawave.github.io)
 (TXT) w3m dump (kaleidawave.github.io)
        
       | skybrian wrote:
       | > Like sets, types can be by description have an infinite number
       | of distinct entries
       | 
       | I think they might have meant "entities" instead of "entries?"
       | 
       | The term "diagonal identity" seems to be non-standard as well?
        
         | dec0dedab0de wrote:
         | I usually say items or members, but entries basically means the
         | same thing, and js set objects have an entries method, so there
         | is precedence.
        
       | throwaway17_17 wrote:
       | I don't think it is appropriate to say Rust has 'union types'.
       | Rust has sum types, implemented as Enums and (unsafe) Union
       | types. There is a distinct difference between sum types and union
       | types from a type theoretic perspective.
        
       | o11c wrote:
       | `never` is better known as `bottom`. `noreturn` in some languages
       | is the same thing
       | 
       | `any`, however, is not `top`, it is `break_the_type_system`. The
       | top type in TS is `unknown`.
        
       ___________________________________________________________________
       (page generated 2024-10-31 23:00 UTC)