Re: [gwt-contrib] Re: What constitutes an acceptable emulated String.format implementation?

2015-02-12 Thread James Nelson
I know that adding more magic methods is generally frowned upon, but the advantage here is that a String literal can be made available at compile time, allowing the injection of a minimal-overhead replacement. If, for any reason, the String is not a literal, we can emit a warning about the runtim

Re: [gwt-contrib] Re: What constitutes an acceptable emulated String.format implementation?

2015-02-10 Thread Colin Alworth
I'd be strongly in favor of a StringFormat class - this could be library-ized easily, letting someone opt in to even having it in their project, or call it. Since we're changing the API (though I assume keeping the 'format string' language), you could take other steps to ensure small complied size

[gwt-contrib] Re: What constitutes an acceptable emulated String.format implementation?

2015-02-10 Thread Benjamin DeLillo
If trying to provide a fairly complete duplicate of the JRE functionality is too much of a point of contention, would it be more acceptable to provide a simpler/lighter-weight string interpolation implementation behind e.g. GWT.format() or to follow the NumberFormat convention a StringFormat cl