> While I do think that NULL is a hard to deal issue in many languages and I admire languages like Rust without NULL, Why would you admire this? Dropping .unwr

> While I do think that NULL is a hard to deal issue in many languages and I admire languages like Rust without NULL, Why would you admire this? Dropping .unwrap().wrap() on all the things is not any better than doing the same thing on nullable types. "duh you're meant to handle them straight away so its not an issue" - no shit? Do you think maybe the same could be said about null values? Removing optionality from a type system is a mistake, it just leads to more gibberish to handle undefined/notset. > EdgeQL is slightly different. As you noticed, we do have a concept of empty set, which in some ways is similar to NULL in SQL (with the caveats I explained above). Yes, it is slightly different, no it is not similar to null. It is what you get when you don't have null and don't have options. i.e. no sentinel, just a maybe.