[LOG4J2-1329] API change: let Message.getFormattedMessage() return CharSequence instead of String

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.5
• Component/s: API
• Epic Link: GC-free
• Assignee: Unassigned
• Reporter: Remko Popma
• Created: 23/Mar/16 07:37
• Updated: 13/Apr/16 15:55
• Resolved: 28/Mar/16 14:26

Description

I propose that we change Message.getFormattedMessage() to return a CharSequence instead of a String.

I believe this change would be backwards compatible (all Message implementations that return a String will work as is), and it opens the way
for zero-GC Message implementations to return a cached StringBuilder as Mikael suggested on the log4j-dev mailing list.

Issue Links

• relates to: LOG4J2-1326 API change: add methods for logging CharSequences (was: Provide support for CharSequence parameters for low and zero-GC applications)