... Looks nice! I have some questions though, * I assume slice will modify the receiver and viewSlice won't ? * Any chance for the splice method? * Are the...
... yes. ... What does that do? Do you mean join()? ... last and first don't modify the receiver. I like the idea of a pop method. ... Interesting idea! The...
... I don't understand. Presumably this must be different from projectiles clone select(visible) foreach(redraw) or else you wouldn't be suggesting it, would...
... There are 2 important differences: - it works on Strings (which are immutable) - it's more efficient than operations like "clone select" in cases where the...
... But I can already clone strings without any problem, and it works just the way I'd expect: Io> j := "a" ==> a Io> j ==> a Io> k := j clone ==> a Io> k =...
... Yes, but you can't do mutable operations on them. With the current interface, we have the following problem: mutation methods like: removePrefix("foo") are...
... Yes, excellent. Thanks. But I'm a bit worried about the name of the new method: you had to explain to me how cloneRemovePrefix differs from clone...
... I'm going to dissent and say no. Abstractly, immutability is a (potential) property of any given object, and one that is quite rare at that. Some...
... Yes, we should consistently have something in the method names that: 1. distinguishes clone operations (in-place operations are the default), or 2....
... In the interest of small, 3 should be discarded immediately. ... This I agree with. ... The case against is that you get *nothing* by having the additional...
... I agree the 'clone' seems clunky. What about making the mehtods past tense? There's already a 'capitalized', and I know that it returns a new string. ...
... Doc, It's more general than that. Consider: listOfBuffers foreach(removePrefix("foo";)) and: listOfStrings foreach(removePrefix("foo";)) and notice that the...
... It seems to me that this problem could be resolved by having all the methods return the modified object, and therefore having the iterators replace the...
... It's more general than that. Consider: listOfBuffers foreach(removePrefix("foo";)) and: listOfStrings foreach(removePrefix("foo";)) and notice that the...
... Actually, the opposite is true. You didn't crash the C code at all, instead it exited (I guess) via an Io exception. The back trace shows the stack from...
... OK, but I don't understand what you want those examples to *mean*. For the first, the current and "new" (as I posit) behavior seems to be as expected: the...
... I agree with all of those points, but the problem remains that cloneFoo looks like it does the same thing as clone foo, but it doesn't always. So I suggest...
... And *that* is *my* reason for not liking it: it does the same thing. You're adding things to methods that don't add anything. Then you go and add methods...
... It's a good idea, but the rule: - add "clone" to the front of the method name seems simpler than: - somehow rearrange the words and add an "ed" -- Steve...
Then again, you do speak English, and verb tenses aren't really that complex when you're practised. I like the way it reads, certainly. ... ___________________...
