implement an owned rope type

[thestinger]

This should just be a generic sequence type, and we can build an actual string on top of it later as we do on top of the byte vector representation. Of course, starting off with just sequences of bytes and extending it later would be fine.

[huonw]

Traige visit; still valid.

[bytbox]

Is anyone currently working on this? I'm considering taking this up.

[huonw]

@bytbox I haven't heard of anyone working on it.

[swgillespie]

Looks like this issue has been abandoned since 3 months ago, I'd like to take a swing at this if no one else is working on it.

[bytbox]

Yup. Go right ahead.

Actually, here's my code, just in case you want to take a look. http://ix.io/bCF

[apollow]

@swgillespie Are you still working on this? I've got interest in working on it if you aren't, just got a little bit of code worked on it so far

[swgillespie]

I was pretty unsuccessful so by all means, go for it!

[ftxqxd]

@apollow Have you stopped working on this? I’ve been playing around and I’ve got something working. (Here’s the code so far and an example of a rope’s graph.)

Should this be in its own crate or just in libstd (or libtext when that happens)?

[apollow]

I'm still working on it, I'll take a look at your code as well, just got down conceptualizing how cords get balanced and working on compare to get some tests out, we should definitely collab on this!

[SSheldon]

Wow, uh, my bad, I had assumed this was dead and had also been working on a basic implementation that I was about to pull request before I checked back on this issue 😛

Sounds like @apollow and @P1start have got this under control, but here's what I had in case there's anything you all find useful: https://github.com/SSheldon/rust/compare/master...rope

[apollow]

Posting to reassure that this has not been abandoned! Finally got back some time to continue working on this: I hope to finish my portion by next week weds.

Update: Finally got something compiling for the balance portion of rope. Will get to testing soon!

Update Oct 20 and reminder for myself: Going to need a paired prog session with P1Start, then some finalizations on testing before any progress forward

[steveklabnik]

I'm pulling a massive triage effort to get us ready for 1.0. As part of this, I'm moving stuff that's wishlist-like to the RFCs repo, as that's where major new things should get discussed/prioritized.

This issue has been moved to the RFCs repo: rust-lang/rfcs#653