Reading the documentation using String.contains is...

# arrow-meta

[Ties]

Reading the documentation using String.contains is not (yet) possible:

@JvmInline
    value class Email(val value : String) {
        init {
            require(value.contains("@")) { "Email should be valid" }
        }
    }

But require is also a kotlin thing to throw an exception. If I want to do this my code no longer compiles because arrow-analysis cannot work with this.
Does this mean that for now I should not include arrow-analysis in code that contains require keywords (with invalid constraints) or is there a way to exclude those?
It is not really a use-case for me, but I want to give a talk about arrow-analysis and im just curious about the current limitations (Because I am quite excited about the stuff it brings)