As of now I find that the Ops matcher hides/conceals too much error information when it determines that no match can be made. See, for example, here, where the Op Matcher completely disregards the OpMatchingException.
This is less of a question of dumping out all of the information but more about being smarter about what we dump out. For example, we will be traversing the code linked above many times, and most of those times we will be attempting a transformation for which there will be no matching Op. This is what the OpMatchingException will say. Of course we (probably?) do not want printouts for each attempted transformation due to the sheer amount of attempts that might happen. However we might have great interest in an OpMatchingException stating that there are two allowable matches. This is something that, unless one debugs the code, might be easily overlooked because this information is automatically ignored.
In this way a discussion might be in order as to what information should be printed out.
As of now I find that the Ops matcher hides/conceals too much error information when it determines that no match can be made. See, for example, here, where the Op Matcher completely disregards the
OpMatchingException.This is less of a question of dumping out all of the information but more about being smarter about what we dump out. For example, we will be traversing the code linked above many times, and most of those times we will be attempting a transformation for which there will be no matching Op. This is what the
OpMatchingExceptionwill say. Of course we (probably?) do not want printouts for each attempted transformation due to the sheer amount of attempts that might happen. However we might have great interest in anOpMatchingExceptionstating that there are two allowable matches. This is something that, unless one debugs the code, might be easily overlooked because this information is automatically ignored.In this way a discussion might be in order as to what information should be printed out.