A modern programming language that makes developers happier.

kotlinlang

is there some heuristic whereby it makes sense that collections.last() is a function but size is a property?

<https://kotlinlang.org/docs/coding-conventions.html#functions-vs-properties>
`last()` throws, `size` doesn't

I think there are some parts of stdlib where it's arguably inconsistent - e.g. `isEmpty()` - but lots of parts of Kotlin pre-date the modern style document

I was attempting to justify in my mind why `isEmpty` would be a method, but nope I can't find any reason. It doesn't do any expensive or long computation in the case of normal collections (just a size check) or Iterables/Sequences (just a `hasNext`) check. Sure, hasNext theoretically could be "expensive", but I don't think that justifies it.

... wait, why isn't hasNext a property? :face_palm:

arguably, `hasNext()` can be expensive, e.g.
```generateSequence(2.toBigInteger()) { it.nextProbablePrime() }.iterator().hasNext()```
but that doesn't apply to `isEmpty()` since that's a method on `Collection` and other types with a `size`