I don't think parent did mean that he had a "right" to expect some level of quality or anything. It's just that we, as programmers, tend to take measures so th

I don't think parent did mean that he had a "right" to expect some level of quality or anything. It's just that we, as programmers, tend to take measures so that silly bugs do not happen anymore or that, at least, we leave big clues as to what went wrong. In a project I had a similar issue: I was wrapping lists inside immutable lists but, due to a silly bug, I kept wrapping immutable lists inside immutable lists at every save made. So saved files would grow bigger and bigger. And I did fix the bug and also added a big fat warning logs in case too many nested lists were detected. pg might just as well have now added something preventing infinite recursion inside the comment tree or some WARN logging telling when a generate page is getting too big, etc. I'd still find it very interesting to know what pg did, if any, to dodge / minimize / make it easier to determine if such an issue happens in the future.