Christoph Lipka

For the records: I'm filing this under "let's not put this on our plate for the v3.8.0 release", because it is presumably behavior carried over from v3.7, and certainly not...

Is this something anyone else has ever observed?

Is this a regression from v3.7.0?

This looks easy enough to fix in passing before we release v3.8.0.

@chris20 Has this ever come to fruition?

To pick up on the old discussion, let's examine the situation more closely: The current implementation seems to be primarily geared towards situations where multiple `#debug` statements are used to...

For the records: Since this is long-standing behavior, I don't think there's much need to do anything about this in v3.8.0.

Someone should check whether we've already added this.

> Ehhh, don't know. I think a cut off more automatic and intensity based would be better - would need to think some about how to do that safely. The...

Someone should check whether the mentioned solution has already found its way into the v3.8 branch.