The code would assume that SubstExpr() cannot fail on concept
specialization. This is incorret - we give up on some things after fatal
error occurred, since there's no value in doing futher work that the
user will not see anyway. In this case, this lead to crash.
The fatal error is simulated in tests with -ferror-limit=1, but this
could happen in other cases too.
We need want to pass -verify to clang for these directives to have an effect.
The fatal error can be matched by // expected-error@* {{too...}} (maybe that's obvious, but it took me some time to figure it out first time I needed it)
And there is no need to run FileCheck after that!