So I would like to understand (sincerly) what was the problem and what is the gain? I learned that we can ask a collection a readStream and writeStream already. And now we can do anyCollection readStreamDo: and writeStreamDo: Why not? On Sat, Dec 16, 2017 at 4:42 PM, Stephane Ducasse <stepharo.self@gmail.com> wrote:
Hi
Do we really want this? I do not understand why a string is a fileReference? String has far too many methods and we are even adding more and I do not understand why.
Stef
On Thu, Dec 14, 2017 at 12:01 PM, <ci-pharo-ci-jenkins2@inria.fr> wrote:
There is a new Pharo build available!
The status of the build #381 was: SUCCESS.
The Pull Request #605 was integrated: "20796-String-should-understand-readStreamDowriteStreamDo-to-be-polymorph-with-FileReference" Pull request url: https://github.com/pharo-project/pharo/pull/605
Issue Url: https://pharo.fogbugz.com/f/cases/20796 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20...