This kind of function overload is present everywhere in the Java collection framework (and probably other libraries). It is a performance optimization (variadic

This kind of function overload is present everywhere in the Java collection framework (and probably other libraries). It is a performance optimization (variadic arguments in Java require creating an array), and variadiac overloads also exist (Map.of needs a list of Map.Entry for type safety) for creating collections of any size. https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/util/List.html#of(E,E,E,E,E,E,E,E,E,E) https://docs.oracle.com/en/java/javase/11/docs/api/java.base...