In Google Guava (Java), why are Iterables.getFirst() and getLast() inconsistent?

Question

From Google Guava JavaDoc for Iterables:

static <T> T getFirst(Iterable<T> iterable, T defaultValue)

-> Returns the first element in iterable or defaultValue if the iterable is empty.

static <T> T getLast(Iterable<T> iterable)

-> Returns the last element of iterable.

static <T> T getLast(Iterable<T> iterable, T defaultValue)

-> Returns the last element of iterable or defaultValue if the iterable is empty.

One static method is missing (to me):

static <T> T getFirst(Iterable<T> iterable)

-> Returns the first element of iterable.

Do you know the reason for this inconsistency?

Sean Owen · Accepted Answer · 2011-10-20T08:43:40.087

24

Because it's too simple to justify a helper method. The method would just be iterable.iterator().next() and would have behavior exactly analogous to getLast().

edited Oct 20 '11 at 08:43

answered Oct 20 '11 at 07:39

Sean Owen

66,182
23
141
173

3

Strictly speaking it would be `iterable.iterator().next()`, but I agree. – Joachim Sauer Oct 20 '11 at 07:48
Ah of course, typed too fast. I'll fix that. – Sean Owen Oct 20 '11 at 08:43
13

Still, when using methods like `Iterables.getLast()`, I'd assume the method to be present just for code readability and intent expression... – Petr Janeček Jan 10 '13 at 01:24

In Google Guava (Java), why are Iterables.getFirst() and getLast() inconsistent?

1 Answers1

Linked