News for hackers. Stuff that matters.
Re:A convenient untruth: Array notation in C is a lie by unscaled on Thursday December 22, 2016 @04:45PM (#13240655)
Well, had C been really strongly-typed then the hypothetical 'int[5]' and 'int[7]' would have been different types, and 'int[]' would be the size-agnostic type for an array.

Then you could easily get creature comforts such as:

  typedef uint8_t[16] guid_t;
  typedef uint8_t[20] sha1_digest_t;
These typedefs would then have copy assignment, pass-by-value semantics and everything else you'd expect from value types.
Re:A convenient untruth: Array notation in C is a lie by ssalazar on Thursday December 22, 2016 @06:36PM (#13241476)
> Then you could easily get creature comforts such as:

    > typedef uint8_t[16] guid_t;
    > typedef uint8_t[20] sha1_digest_t;
> These typedefs would then have copy assignment, pass-by-value semantics and everything else you'd expect from value types.

What does this accomplish that a struct can't?