[trixie_]

The type definition alone wouldn't tell you if it's an enum, ordered, or no duplicates allowed...

The writer would know what type they're working with through intellisense. The reader would know it's iterable based on just reading the code that follows it..

So again, what does the type info give you? Most of what you mentioned you wouldn't be able to figure out from just a type name...

[exabrial]

List<> tells me it's an ordered collection of a singular superclass that allows duplicate instances.

var tells me nothing.

[trixie_]

'var transactions' is enough information for most people to understand it's a list of some sort. If it really matters to you then use the IDE. The full type info is just not that useful. That's why most languages are moving towards inferred typing - typescript, c#, java, c++, rust, go, scala, etc...

[exabrial]

And the fact we're (amicably) disagreeing just proves I'm right. List<> leaves no ambiguity

[exabrial]

How do you know it's not a count of the transactions?