RSSMastodonDiscordMediumYouTubeTwitchGitHubStackOverflow

How Project Valhalla And JSpecify Can Kill NPEs

//
#project‑valhalla#libraries#conversation

Project Valhalla's value types need to be aware of which instance can be null and which can't, so the JVM can inline them. So will Java get a null-aware type system after all? Not quite, but it may get close and JSpecify can help with some of those steps.

Always embed videos

(and give me a cookie to remember - privacy policy)

Watch on YouTube

How Project Valhalla And JSpecify Can Kill NPEs

Share this post with your community:

I'm active on various platforms. Watch this space or follow me there to get notified when I publish new content:

▼

Share this post with your community:

I'm active on various platforms. Watch this space or follow me there to get notified when I publish new content:

Hey, I'm nipafx, but you can call me Nicolai and today it's gonna be you, me, Kevin Bourrillion, and Project Valhalla, specifically its interest in and intentions for null. As I'll explain in a minute, Valhalla needs to know which value type instances can be null and which can't, so it can inline them. There have been different ideas for how to do that, but the most recent one proposes to introduce question mark and exclamation mark, or bang, as modifiers for value types. Then, for example, an Integer! could be treated as an int and we'd get similarly performant behavior for non-null instances of our own value types.

Now, tracking null is also something that IDEs and tools can do for you, but they're not quite aligned on how they do that and there are various discrepancies. A standard is needed and together with other people, Kevin is working on that in JSpecify. A few months ago, he presented it on my Twitch channel and I uploaded most of his presentation earlier this week - give it a watch if you want to know the goal, design, and progress of JSpecify.

In that video, I left out the section of his presentation that revolved around the overlap between JSpecify and Valhalla as well as our conversation about that topic, for example how JSpecify could help with a hypothetical expansion of question mark and bang to reference types. This video here are those parts stitched together, but I took the freedom to rearrange them for a better structure, so please forgive the occasional dangling pointer to something that's missing or comes later. So, here it is: Java, null, JSpecifcy, and Project Valhalla. Enjoy!

You might have noticed on the screen behind me that I had a second guest on. That was Manu Sridharan of NullAway fame. He's one of the other contributors to JSpecify and he had more to say on non-Valhalla topics in the Q&A after Kevin's presentation, where I and the stream audience got to ask all kinds of questions about JSpecify. I hope to upload that next week, but it's quite a bit of work. I think a few likes on this video could really motivate me to spend my weekend on that. So long ...