this post was submitted on 09 Feb 2026
4 points (100.0% liked)

Programming

25477 readers
290 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] justicecoder@programming.dev 2 points 2 days ago (1 children)

Let me correct a misunderstanding. JADEx was created as a Java superset language to strengthen Java’s insufficient null-related type system. In JADEx, Java’s reference types are assumed to be non-null by default, and through the nullability static analysis results provided by JADEx, developers can explicitly choose to mark types as nullable. Because of this, there is no problem using null-safe access operators and the Elvis operator.

To summarize:

  • Java: All types are nullable; there is no non-null type. Therefore, Elvis operators and null-safe access operators cannot be used.
  • JADEx: Both nullable and non-null types exist. Therefore, Elvis operators and null-safe access operators can be used.
[–] lambdabeta@lemmy.ca 1 points 2 days ago (1 children)

Good clarification, thank you. I guess it would still require some extra care when interfacing with plain Java libraries, but so does e.g. Kotlin. Cool implementation.

[–] justicecoder@programming.dev 1 points 2 days ago

We hope you continue to show great interest in JADEx. Thank you :)