@NotNull annotations are not used in jbanking : so far keeping the library completely dependency-free was preferred. But this annotation helps static code analysis, can be really helpful in IDEs or with some languages like Kotlin.
Or switch to Kotlin for its null-safely and less boilerplate, targeting the JVM only first, but eventually opening the target audience to multi-platform?
@NotNull
annotations are not used in jbanking : so far keeping the library completely dependency-free was preferred. But this annotation helps static code analysis, can be really helpful in IDEs or with some languages like Kotlin.Should we consider using
@NotNull
annotations ?