[Pharo-dev] feenk log

2018-08-16 Thread Tudor Girba
Hi, We again got carried away and forgot to update the world about what is up in our corner. Here is a summary: -- Bloc & Brick -- - Text editor stability has been significantly improved - Improved support for selection in the text editor - Support for typical editing keybindings (copy, cut,

Re: [Pharo-dev] Collection groupedBy: and groups order

2018-08-16 Thread Chris Muller
Despite the interleavement, the order of the grouped elements as they occurred in the original collection could be preserved. On Wed, Aug 15, 2018 at 6:34 AM, Damien Pollet wrote: > The problem is, there isn't really an order to preserve in the first place, > since even if the original

Re: [Pharo-dev] Collection groupedBy: and groups order

2018-08-16 Thread Petr Fischer via Pharo-dev
--- Begin Message --- I created two tests, here: Gofer it url: 'https://dev.cvokhaus.cz/st-public/'; package: 'CollectionGroupedByOrderTest'; load. What do you think? pf > Hi Petr > > do you have a test illustrating what behavior you think should be good? > > Stef >

Re: [Pharo-dev] Collection groupedBy: and groups order

2018-08-16 Thread Stéphane Ducasse
Hi Petr do you have a test illustrating what behavior you think should be good? Stef Stéphane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59

[Pharo-dev] [Pharo 7.0-dev] Build #1174: 22315-remove-implicit-requirement-from-traits

2018-08-16 Thread ci-pharo-ci-jenkins2
There is a new Pharo build available! The status of the build #1174 was: SUCCESS. The Pull Request #1686 was integrated: "22315-remove-implicit-requirement-from-traits" Pull request url: https://github.com/pharo-project/pharo/pull/1686 Issue Url: https://pharo.fogbugz.com/f/cases/22315

[Pharo-dev] [Pharo 7.0-dev] Build #1173: 22314-Stdio-doesnt-handle-cygwin-terminals-correctly

2018-08-16 Thread ci-pharo-ci-jenkins2
There is a new Pharo build available! The status of the build #1173 was: FAILURE. The Pull Request #1684 was integrated: "22314-Stdio-doesnt-handle-cygwin-terminals-correctly" Pull request url: https://github.com/pharo-project/pharo/pull/1684 Issue Url:

Re: [Pharo-dev] Association hash vs equality

2018-08-16 Thread Guillermo Polito
Actually, #= and #hash should be defined so: if (a=b) then a hash = b hash if a != b, it's not important This is required because some collections (like sets, dictionaries) will index their elements by their hash. Then, typically the collection implementation will first ask the hash, access the

[Pharo-dev] Association hash vs equality

2018-08-16 Thread Jan Blizničenko
Hello, I've been looking at implementation of Associtation and LookupKey (its superclass). In LookupKey, there is LookupKey>>#= and LookupKey>>#hash both implemented to use key (compare keys and use hash of key), but in Association, Association>>#= compares both key and value, but hash is not

[Pharo-dev] [Pharo 7.0-dev] Build #1172: 22307-Refactoring-doesnt-work-in-debugger---Walkback-dnu-contentSelection

2018-08-16 Thread ci-pharo-ci-jenkins2
There is a new Pharo build available! The status of the build #1172 was: FAILURE. The Pull Request #1680 was integrated: "22307-Refactoring-doesnt-work-in-debugger---Walkback-dnu-contentSelection" Pull request url: https://github.com/pharo-project/pharo/pull/1680 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #1171: 22312-Integrate-Iceberg-v122

2018-08-16 Thread ci-pharo-ci-jenkins2
There is a new Pharo build available! The status of the build #1171 was: SUCCESS. The Pull Request #1682 was integrated: "22312-Integrate-Iceberg-v122" Pull request url: https://github.com/pharo-project/pharo/pull/1682 Issue Url: https://pharo.fogbugz.com/f/cases/22312 Build Url: