Currently we only have the --disable-api-has-check-removal and thus we can either enable or disable it totally in the whole build. However it would be useful if we had a way to be more granular and let the compiler know which parts of our code (aka which has checks) to optimize out at compile time and which not.
I don't know if that would be possible, but an idea: use an annotation, similar to (:typecheck(false)), i.e: (:has_check_removal(false))
This is still not 100% granularity, but it's a pretty good way, because we can use it on a per function basis, and often one function only uses one "type" of has checks that we want to treat similarily (and if not, then it can be refactored :)
