---
title: "Comment by Ryan Hintze on \"Extending Kotlin's Null-Safety with Monad Comprehension\" | Hashnode"
description: "Enjoyed the article! What do you think of using contracts for nullable values instead of using the result of bind ? I can only think that this might cause some"
url: "https://hashnode.com/posts/extending-kotlins-null-safety-with-monad-comprehension/65f73c77684cee4498a73d43/comment/65f86e358b3ed7f936c93daf"
---

[Discussion](https://hashnode.com/posts/extending-kotlins-null-safety-with-monad-comprehension/65f73c77684cee4498a73d43)

Comment [Extending Kotlin's Null-Safety with Monad Comprehension](https://hashnode.com/posts/extending-kotlins-null-safety-with-monad-comprehension/65f73c77684cee4498a73d43)

[Ryan Hintze](https://hashnode.com/@spyderrsh)

Android Software Engineer. Lover of Kotlin.

[Mar 18, 2024](https://hashnode.com/posts/extending-kotlins-null-safety-with-monad-comprehension/65f73c77684cee4498a73d43/comment/65f86e358b3ed7f936c93daf)

Enjoyed the article! What do you think of using contracts for nullable values instead of using the result of `bind`? I can only think that this might cause some issues if a background thread or value read changes the value. I implemented a PoC here:

https:// github .com/spyderrsh/extending-kotlin-null-safetly/commit/40fc29336725f2e4c7fdd353c062973405a356a6

(Sorry, new user, so I had to add spaces in my link)