8567402969
This commit extract spring-related links and recurring external links into asciidoctor attributes to be used by the Antora toolchain. It notably homogenizes links to: - IETF RFCs - Java Community Process JSRs - the Java API Documentation (on the Java 17 version) - Kotlin documentations (on the Kotlinlang.org version) - the Spring Boot reference guide (on the `html` version) This commit also reworks most link attributes to follow a Project-Category-Misc syntax. For example, `spring-boot-docs` rather than `docs-spring-boot`. Finally, it makes an effort to clean up remainders from the previous documentation toolchain, namely the `docs/asciidoc` folder and `modules/ROOT/pages/attributes.adoc` file. Closes gh-26864 Closes gh-31619
39 lines
2.1 KiB
Plaintext
39 lines
2.1 KiB
Plaintext
[[kotlin-null-safety]]
|
|
= Null-safety
|
|
|
|
One of Kotlin's key features is {kotlin-docs}/null-safety.html[null-safety],
|
|
which cleanly deals with `null` values at compile time rather than bumping into the famous
|
|
`NullPointerException` at runtime. This makes applications safer through nullability
|
|
declarations and expressing "`value or no value`" semantics without paying the cost of wrappers, such as `Optional`.
|
|
(Kotlin allows using functional constructs with nullable values. See this
|
|
{baeldung-blog}/kotlin-null-safety[comprehensive guide to Kotlin null-safety].)
|
|
|
|
Although Java does not let you express null-safety in its type-system, the Spring Framework
|
|
provides xref:languages/kotlin/null-safety.adoc[null-safety of the whole Spring Framework API]
|
|
via tooling-friendly annotations declared in the `org.springframework.lang` package.
|
|
By default, types from Java APIs used in Kotlin are recognized as
|
|
{kotlin-docs}/java-interop.html#null-safety-and-platform-types[platform types],
|
|
for which null-checks are relaxed.
|
|
{kotlin-docs}/java-interop.html#jsr-305-support[Kotlin support for JSR-305 annotations]
|
|
and Spring nullability annotations provide null-safety for the whole Spring Framework API to Kotlin developers,
|
|
with the advantage of dealing with `null`-related issues at compile time.
|
|
|
|
NOTE: Libraries such as Reactor or Spring Data provide null-safe APIs to leverage this feature.
|
|
|
|
You can configure JSR-305 checks by adding the `-Xjsr305` compiler flag with the following
|
|
options: `-Xjsr305={strict|warn|ignore}`.
|
|
|
|
For kotlin versions 1.1+, the default behavior is the same as `-Xjsr305=warn`.
|
|
The `strict` value is required to have Spring Framework API null-safety taken into account
|
|
in Kotlin types inferred from Spring API but should be used with the knowledge that Spring
|
|
API nullability declaration could evolve even between minor releases and that more checks may
|
|
be added in the future.
|
|
|
|
NOTE: Generic type arguments, varargs, and array elements nullability are not supported yet,
|
|
but should be in an upcoming release. See {kotlin-github-org}/KEEP/issues/79[this discussion]
|
|
for up-to-date information.
|
|
|
|
|
|
|
|
|