ropey
ropey copied to clipboard
cessen
A utf8 text rope for manipulating and editing large texts.
Currently the `Lines` iterator is roughly equivalent to just calling `Rope::line()` repeatedly with an incrementing index. This is O(log N) for each call to `Lines::next()`, and also is just generally...
Closes #82. I decided to make a struct `TwoWayPeekable` which will contain the iterator and the peeked value, similar to `std::iter::Peekable`. This allows to eliminate code duplication and this way...
Hello cessen, How do you traverse the `Chunks` and get the byte/char/line index of those chunks? That would be awesome if `Chunks: Iterator`! Is this desirable/achievable? Do you think it's...
In https://github.com/cessen/ropey/issues/18#issuecomment-522326596 there was a discussion about adding `.peek_next()` and `.peek_prev()` methods to iterators, but they were never added. And I'd like them to be added, because I have to...
ropeys line iterator doesn't do so well compared to other ropes and I always wondered why. My recent work on a streaming regex engine made clear to me why: The...
When using panicking versions of the `Rope` methods, IMO it's better to get the location where you didn't respect the invariants that lead to the panic over the location of...
I tripped over the fact that an empty buffer will return a line from the `lines` iterator. It was a bit unexpected since it deviates from the behavior of `str::lines`...
