Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Fix another markup problem #729
Sorry I missed this in the earlier PR. There was a markup error (a glossterm'd static-error that wasn't in an error element) and that made me look more closely at the paragraph.
I've reworded it slightly to improve the English.
I have a question though, why is the case of type errors being called out specifically here. We have a rule that says dynamic errors can be raised statically if the processor can prove they will always occur, does that rule not apply to type errors? If not, why not?
If we do not call out type error here the behaviour of a pipeline changes if you switch from Saxon EE (static typing feature implemented -> typing error raised statically) to Saxon HE (error raised dynamically).
Did I miss something?