any operand in clvm is evaluated eagerly, so operations like these can easily be combined using any of multi-arg operator. But perhaps the most convenient would be the function proposed for the standard library (filtermap (bls_verify ...) (list conditions...))
raising on failure eliminates a class of errors (it's debatable how important it is though)
raising on failure guides people towards setting up their puzzles and solutions such that you always know that a verification will pass, or avoid running it at all, which I believe is best practice.
raising on failure (and returning nil) is compatible with unknown operators, and allows future verification operators to follow the same pattern and be soft-forked in outside of the softfork-guard. secp256 is a likely future candidate.
These are some of the important points:
(filtermap (bls_verify ...) (list conditions...))
softfork
-guard. secp256 is a likely future candidate.