mikkorantalainen commented on pull request #630:
URL: https://github.com/apache/logging-log4j2/pull/630#issuecomment-1039259530
> I am also inclined to avoid convoluting the API with implementation
details. Messages are safe, it is how the implementation deals with them which
makes them
mikkorantalainen commented on pull request #630:
URL: https://github.com/apache/logging-log4j2/pull/630#issuecomment-1039259530
> I am also inclined to avoid convoluting the API with implementation
details. Messages are safe, it is how the implementation deals with them which
makes them
mikkorantalainen commented on pull request #630:
URL: https://github.com/apache/logging-log4j2/pull/630#issuecomment-996316597
I think InterpretedMessage would be problematic, too, because it can be
understood as "message to be interpreted in the future" or "message that has
already been
