Bug 440612

Summary:	Use StringBuilder instead of StringBuffer in Handle 'toString' methods
Product:	[Technology] Handly	Reporter:	Vladimir Piskarev <pisv>
Component:	Core	Assignee:	Vladimir Piskarev <pisv>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	Keywords:	api
Version:	0.1
Target Milestone:	0.2
Hardware:	All
OS:	All
Whiteboard:	breakingchange

Description Vladimir Piskarev

2014-07-29 03:45:01 EDT

This StringBuffer usage was inherited from some old code, we should exterminate it from API (and implementation) until it is too late.

Comment 1 Vladimir Piskarev

2014-07-29 04:01:51 EDT

Note that this will break binary compatibility with the previous release (0.1). I think it's a reasonable trade-off in this case since there would be too many 'toString' methods to deprecate and we have been explicit in making no API promises for 0.1.

Comment 2 Vladimir Piskarev

2014-07-29 04:07:59 EDT

I forgot to add that migration path for existing clients should be very easy too.

Comment 3 Vladimir Piskarev

2014-07-29 04:15:00 EDT

Pushed to master.