Sybex 819, Chapter 14, Table 14.7

[Taiwo Ajayi]

Table has method definition written in short form as

void forEach(BiConsumer(K key, V value)) 

which appears to be a bit confusing as BiConsumer seems to look like a method (rather than a functional interface) with two parameters, especially if needed to be consistent with the other table entries.

Perhaps better written as

void forEach(BiConsumer<K, V> loopaction) 

[Mikalai Zaikin]

I don't have the book, but based on your input I agree.

One more thing: to avoid confusing, please do not use K(ey) / V(alue) type parameters for BiConsumer.

Consumer and BiConsumer may accept some parameter(s), so, a plain parameter usually denoted T(ype), and if you need a second, then used the next letter in the alphabet U, then V, and so on...

These declarations are better IMHO

Consumer<T>
BiConsumer<T,U>

P.S. this is just a convention, not mandatory, simply to avoid confusion.

<K,V> things are applicable to Map, HashMap, etc..

[Taiwo Ajayi]

Thanks for your comments. The table was describing map methods, hence the conventional K, V being used.

[Jeanne Boyarsky]

Yech. In addition to being confusing, it is wrong. forEach() and merge() have that problem in the Java 17 book too. (table 9.6 there). I've added this to the errata of the Java 11 and 17 books and credited you