- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Collection groupedBy: and groups order
by Damien Pollet Aug. 17, 2018

Aug. 17, 2018

The problem is, there isn't really an order to preserve in the first place, since even if the original collection is a sequencable one, the elements of each group would be interleaved in it. I could see the point of sorting the keys though. On Tue, 14 Aug 2018 at 18:32, Petr Fischer via Pharo-dev < pharo-dev(a)lists.pharo.org> wrote: > Hello, I found a useful method in the collection - groupedBy: - the result > container is some PlugableDictionary (integer variant) and group order > (keys) is not preserved. > > Would not it be better to choose some other Dictionary variant, which > preserve the order of groups (like in source Collection)? > > pf > > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

3 2

[Pharo 7.0-dev] Build #1176: 22335-Add-Spec-Demo
by ci-pharo-ci-jenkins2＠inria.fr Aug. 17, 2018

Aug. 17, 2018

There is a new Pharo build available! The status of the build #1176 was: SUCCESS. The Pull Request #1693 was integrated: "22335-Add-Spec-Demo" Pull request url: https://github.com/pharo-project/pharo/pull/1693 Issue Url: https://pharo.fogbugz.com/f/cases/22335 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[update 6.1] #60542
by Marcus Denker Aug. 17, 2018

Aug. 17, 2018

60542 ----- 22305 Backport to Pharo6: "Leave Variable Undeclared" https://pharo.fogbugz.com/f/cases/22305 <https://pharo.fogbugz.com/f/cases/22305> <https://pharo.fogbugz.com/f/cases/22305> 22298 Backport of the fix of Infinite Debugger https://pharo.fogbugz.com/f/cases/22298 <https://pharo.fogbugz.com/f/cases/22298>

2 2

[Pharo 7.0-dev] Build #1175: 22204 new value holder package should be split into new value holder core and new value holder tests packages
by ci-pharo-ci-jenkins2＠inria.fr Aug. 17, 2018

Aug. 17, 2018

There is a new Pharo build available! The status of the build #1175 was: SUCCESS. The Pull Request #1596 was integrated: "22204 new value holder package should be split into new value holder core and new value holder tests packages" Pull request url: https://github.com/pharo-project/pharo/pull/1596 Issue Url: https://pharo.fogbugz.com/f/cases/22204 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] Collection groupedBy: and groups order
by StÃ©phane Ducasse Aug. 16, 2018

Aug. 16, 2018

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 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

2 1

[Pharo 7.0-dev] Build #1174: 22315-remove-implicit-requirement-from-traits
by ci-pharo-ci-jenkins2＠inria.fr Aug. 16, 2018

Aug. 16, 2018

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 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1173: 22314-Stdio-doesnt-handle-cygwin-terminals-correctly
by ci-pharo-ci-jenkins2＠inria.fr Aug. 16, 2018

Aug. 16, 2018

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: https://pharo.fogbugz.com/f/cases/22314 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Association hash vs equality
by Jan BlizniÄenko Aug. 16, 2018

Aug. 16, 2018

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 changed there, so only hash of key is used, therefore it does not correspond to implementation of method = ... shouldn't it? To demonstrate: (1 -> #a) = (1 -> #b). is false but (1 -> #a) hash = (1 -> #b) hash. is true I also noticed similar discussion for Doplhin smalltalk http://forum.world.st/Association-gt-gt-hash-td3368868.html where guys state it is all right, but I still do not see why. Jan -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

2 1

[Pharo 7.0-dev] Build #1172: 22307-Refactoring-doesnt-work-in-debugger---Walkback-dnu-contentSelection
by ci-pharo-ci-jenkins2＠inria.fr Aug. 16, 2018

Aug. 16, 2018

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: https://pharo.fogbugz.com/f/cases/22307 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1171: 22312-Integrate-Iceberg-v122
by ci-pharo-ci-jenkins2＠inria.fr Aug. 16, 2018

Aug. 16, 2018

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: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0