Hi, > I'm still planning to be the sponsor for this RFE and get this one > > into the jdk9. We are current working on JEP 254 [1][2][3]in which > > the internal storage mechanism is changed from char[] to byte[]. If > > this JEP get approved and is scheduled to target JDK9, the > > decoding/encoding pieces will also need to be updated/ changed > > accordingly. Given that I would prefer to delay this RFE a little > > more till all pieces are settled. > > Do we actually need to wait for Compact Strings to land? The failure > scenario would be that Compact Strings are not making it to JDK 9, and > this code lingers in history. > > I mean it's fine to see if there is a clash between the two, but I don't > think Richard's change should be blocked by Compact Strings, given it is > ready for integration (?), and Compact Strings are not yet.
Thanks for your replies gents - most appreciated. IMO the changes are orthogonal at the moment. If compact strings happen then this patch will probably need to be extended, but I imagine at least the implemented code is the non-compact case and will remain - as would API decisions and Javadoc. Of course that's just my opinion and I'm not as informed on the compact strings work as you are ;) regards, Richard Warburton http://insightfullogic.com @RichardWarburto <http://twitter.com/richardwarburto>
