Please do not use Java 8+ language features or Java 8+ JRE classes/methods, because JOML should have as low of a runtime requirement as possible (being a simple linear algebra library). IMO there is little use in making use of lambda expressions in JOML's code base.
Actually, right now, the minimal necessary Java Runtime Version ist 1.2, because of two things:
the supported for higher runtime is detected at runtime and methods are redirected to those implementations at runtime
the "java6to2" build helper ports down Java 1.6 language features to Java 1.2 (most notably loading named classes at runtime not via the 1.6 "load constant" bytecode instruction but using Class.forName() and replacing uses of StringBuilder with StringBuffer for string concatenations built by the Java compiler)
The only reason the current compile target version is 1.8, is that (sadly) newer JDK versions cannot target 1.6 anymore and with 1.7 we get a deprecation warning, and the Kotlin compiler also cannot target < 1.8.
But IMO there is no real apparent need for having 1.8 language or runtime/classlibrary features in JOML right now.
I am sorry for not having properly announced/documented this.
Please do not use Java 8+ language features or Java 8+ JRE classes/methods, because JOML should have as low of a runtime requirement as possible (being a simple linear algebra library). IMO there is little use in making use of lambda expressions in JOML's code base. Actually, right now, the minimal necessary Java Runtime Version ist 1.2, because of two things:
The only reason the current compile target version is 1.8, is that (sadly) newer JDK versions cannot target 1.6 anymore and with 1.7 we get a deprecation warning, and the Kotlin compiler also cannot target < 1.8.
But IMO there is no real apparent need for having 1.8 language or runtime/classlibrary features in JOML right now.
I am sorry for not having properly announced/documented this.