I expect we may be able to swap in a new String representation in a month
and let the breakage begin. Any code relies on the internal representation
of Strings being specifically Array{Uint8,1} will break, in particular
using the mutability thereof will fail. The I/O stuff is going to take a
lot more work to make things really efficient. The end goal for me is
zero-copy I/O.On Thu, Nov 20, 2014 at 10:58 PM, Pontus Stenetorp <[email protected]> wrote: > On 21 November 2014 03:41, Stefan Karpinski <[email protected]> wrote: > > > > I'm currently working on an overhaul of byte vectors and strings, which > will > > be followed by an overhaul of I/O (how one typically gets byte vectors). > It > > will take a bit of time but all things string and I/O related should be > much > > more efficient once I'm done. There's a lot of work to do though... > > No worries, I think we all understand the amount of work involved in > getting this right and are all cheering for you. I have considered > pitching in with at least some large-scale text processing benchmarks > along the lines of what was discussed in #8826. Hopefully I can get > to this once I get the majority of my current PRs and contributions > settled. > > Pontus >
