equal
deleted
inserted
replaced
204 \begin{isamarkuptxt}% |
204 \begin{isamarkuptxt}% |
205 \noindent |
205 \noindent |
206 What is worth noting here is that we have used \isa{fast} rather than |
206 What is worth noting here is that we have used \isa{fast} rather than |
207 \isa{blast}. The reason is that \isa{blast} would fail because it cannot |
207 \isa{blast}. The reason is that \isa{blast} would fail because it cannot |
208 cope with \isa{someI{\isadigit{2}}{\isacharunderscore}ex}: unifying its conclusion with the current |
208 cope with \isa{someI{\isadigit{2}}{\isacharunderscore}ex}: unifying its conclusion with the current |
209 subgoal is nontrivial because of the nested schematic variables. For |
209 subgoal is non-trivial because of the nested schematic variables. For |
210 efficiency reasons \isa{blast} does not even attempt such unifications. |
210 efficiency reasons \isa{blast} does not even attempt such unifications. |
211 Although \isa{fast} can in principle cope with complicated unification |
211 Although \isa{fast} can in principle cope with complicated unification |
212 problems, in practice the number of unifiers arising is often prohibitive and |
212 problems, in practice the number of unifiers arising is often prohibitive and |
213 the offending rule may need to be applied explicitly rather than |
213 the offending rule may need to be applied explicitly rather than |
214 automatically. This is what happens in the step case. |
214 automatically. This is what happens in the step case. |