That would be ideal, but is very tough. Attempts to do that in the original incarnations of the courses, glossed over many issues and resulted in false positives and negatives.
Best to avoid those, and come up with errors that are accurate, and based on output, not normally on the code itself.
Having said that, there may be a way to improve things, where it shows your output above the expected; same error, really, but would highlight differences a bit more easily. I did that in another challenge in a another course, and it worked great, so may do it here ... a bit tough to do, but possible.
Great that you figured things out, thanks for the suggestion, and the best solution at least for now is to come to this forum for help understanding error messages! Cheers