9

Whyyyyyyyyyy are you making typedefs for a type that you only need once

Just leave the array<uint32, 20> there
It's actually less readable to typedef it

Comments
  • 2
    Damn...a typedef for a specific array is weird.
  • 1
    @iiii my colleague included unit information within in the typedef name, but I would have just out that into a comment

    It's just annoying that the code generator who processes this actually created a typedef in C++, which in the end is nested in like 4 layers.
  • 3
    @LotsOfCaffeine what was it called?array_of_twenty_uint32? 🤣
  • 1
    @iiii more akin to Umilliseconds32Seq
    Which actually is a problem because it sounds like a generic UINT32 sequence and not one that is limited in length, I think I'll just get rid of it.

    I dont why either, this style of naming has been used in the project for a bit now
  • 1
    @LotsOfCaffeine ugly. Bonk him with banhamner on his merge request
  • 0
    Could have become a decent Java coder...
Add Comment