2 comments

  • dfee a day ago ago

    qq: i know nothing about TypeDB, this is a meta-comment, though.

    i've noticed a few times that the author submits something, and makes a comment, and that comment is marked [dead]. is that a bug, policy, or protocol?

  • flyingsilverfin 4 days ago ago

    Hi HN, I work on TypeDB. We recently made a major architectural change to our query language and type system: stripping out implicit optionals and introducing an explicit None type.

    Historically, implicit optionals in our schema design caused a few recurring headaches—most notably not being able to switch on emptiness, and queries silently changing behavior when an existing variable was made optional.

    We looked at how functional languages handle this with explicit Option/None types and decided to bring that strictness to the database level. We actually ended up borrowing the most from languages like Kotlin, using our existing union-of-types model to naturally accommodate the new None type.

    We had a lot of fun wrestling with the semantics and language design while making this change.

    I'd love to hear how others have thought about designing nullability and type strictness. Happy to answer any questions!