September 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo-users] [ANN] RProjectConnector V2.1

by Blondeau Vincent

> -----Message d'origine----- > De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la part de > Serge Stinckwich > EnvoyÃ© : mercredi 14 septembre 2016 15:09 > Ã : Any question about pharo is welcome > Cc : scismalltalk(a)googlegroups.com; Pharo Development List > Objet : Re: [Pharo-users] [Pharo-dev] [ANN] RProjectConnector V2.1 > > Hi Vincent, > Hi Serge, > Ok I try again with the latest Pharo 6.0. > > When I evaluate: > > Gofer it smalltalkhubUser: 'VincentBlondeau' project: > 'RProjectConnector'; configuration; loadStable There is an error : could not > resolve Rconnector. Apparently there is a problem with the package name, > because this vincentBlondeau and not VincentBlondeau (Uppercase). Did you > already try your configuration in an empty Pharo 6.0 image ? :-) Not really for this one ... I corrected and it should work now ;) > > I was able to load RConnector-vincentBlondeau.72 directly from Monticello > repo. > I modify the RLibrary>>macModuleName path name to > /usr/local/Cellar/r/3.3.1_2/R.framework/Versions/3.3/Resources/lib/libR.dyl > ib > When I relaunch my image, I have an error: the R session is not well > initialized at startup. > > In RSession>>isExistsRf_initEmbeddedR I still see a reference to Alien class. > You are still using Alien ? > Because I didn't found something better before. But, I just looked at it and changed to ExternalAddress method. Can you try again with version 73 ? Thanks, Vincent > > > On Tue, Sep 13, 2016 at 6:25 PM, Blondeau Vincent > <vincent.blondeau(a)worldline.com> wrote: > > > > > > > >> -----Message d'origine----- > >> De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part > >> de Serge Stinckwich EnvoyÃ© : vendredi 2 septembre 2016 16:44 Ã : > >> Pharo Development List Cc : scismalltalk(a)googlegroups.com; Any > >> question about pharo is welcome Objet : Re: [Pharo-dev] [ANN] > >> RProjectConnector V2.1 > >> > >> Great job Vincent ! > >> > > It will be great when it will work on OS X ;) > > > >> There is some problems on Mac OS X: > >> - when I try to load in a fresh Pharo 5.0 image, I got a DNU on: > >> RObjectArray class>>initElementType: > >> I was able to load the package after a while by loading directly the > >> package with the Monticello Browser > > > > Strange, I deleted these methods... Please ensure you are using a Pharo 6.0 > image (it should work under Pharo 5.0 too) and that version 14 of > ConfigurationOfRProjectConnector and version 71 of the RConnector > packages are loaded. > > > >> - Apparently there is still some methods using NB like: RSession > >> class>>checkSession or RSession class>>initEmbeddedR: > > > > Should not, it is modified ... > > > >> > >> I try to move the R dll close to my Pharo VM and also inside the > >> Plugins directory but without success ... > > > > It should be at the same location that libcairo.2.dylib > > > >> Is there a way to say where are the R dll instead of copying them ? > >> > > Didn't think so .. Maybe the VM developers knows ? > > > > > > Thanks! > > > > Vincent > > > > > >> Thank you. > >> > >> > >> > >> > >> On Thu, Sep 1, 2016 at 5:42 PM, Blondeau Vincent > >> <vincent.blondeau(a)worldline.com> wrote: > >> > Hello everyone, > >> > > >> > > >> > > >> > I am glad to announce the release of version 2.1 of the > RProjectConnector. > >> > > >> > The binding between Pharo and R (https://www.r-project.org/) is now > >> > translated to UFFI and so to Pharo 6.0. > >> > > >> > > >> > > >> > You can call directly your R methods from Pharo. For example, with > >> > the famous iris clustering example: > >> > > >> > > >> > > >> > iris := 'eval' asREval: {RObject findVar: 'iris'}. > >> > > >> > 'plot' > >> > > >> > asREval: > >> > > >> > {(iris at: 'Petal.Length'). > >> > > >> > (iris at: 'Petal.Width'). > >> > > >> > (#pch -> 21). > >> > > >> > (#xlab -> 'length'). > >> > > >> > (#ylab -> 'Width'). > >> > > >> > (#bg ->((iris at: 'Species') collect: > >> > [ :value | {'red'. 'green3'. 'blue'} at: value ])). > >> > > >> > (#main -> 'Edgar Anderson''s Iris Data')}. > >> > > >> > iris inspect. > >> > > >> > > >> > > >> > To use it, you should install R and copy the R libraries near the > >> > Pharo VM (see the documentation on SmalltalkHub > >> > (http://smalltalkhub.com/#!/~VincentBlondeau/RProjectConnector) for > >> > how to proceed). > >> > > >> > > >> > > >> > Donât forget to relaunch Pharo after the installation to be able to > >> > use the connector. > >> > > >> > > >> > > >> > Only basic features are implemented yet, but you can participate to > >> > its extension! > >> > > >> > > >> > > >> > Cheers, > >> > > >> > Vincent Blondeau > >> > > >> > > >> > > >> > !!!************************************************************ > >> ******* > >> > ****************** "Ce message et les piÃ¨ces jointes sont > >> > confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. > >> > Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous > >> > recevez ce message par erreur, merci d'en avertir immÃ©diatement > >> > l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant > >> > Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra > >> > Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les > >> > meilleurs efforts soient faits pour maintenir cette transmission > >> > exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet > >> > Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout > >> > dommage rÃ©sultant d'un virus transmis. > >> > > >> > This e-mail and the documents attached are confidential and > >> > intended solely for the addressee; it may also be privileged. If > >> > you receive this e-mail in error, please notify the sender > >> > immediately and destroy it. As its integrity cannot be secured on > >> > the Internet, the Worldline liability cannot be triggered for the > >> > message content. Although the sender endeavours to maintain a > >> > computer virus-free network, the sender does not warrant that this > >> > transmission is virus-free and will not be liable for any damages resulting > from any virus transmitted.!!!" > >> > >> > >> > >> -- > >> Serge Stinckwich > >> UCBN & UMI UMMISCO 209 (IRD/UPMC) > >> Every DSL ends up being Smalltalk > >> http://www.doesnotunderstand.org/ > > > > > > > !!!************************************************************ > ******* > > ****************** "Ce message et les piÃ¨ces jointes sont > > confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut > Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce > message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le > dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la > responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de > ce message. Bien que les meilleurs efforts soient faits pour maintenir cette > transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã > cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage > rÃ©sultant d'un virus transmis. > > > > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive this e-mail > in error, please notify the sender immediately and destroy it. As its integrity > cannot be secured on the Internet, the Worldline liability cannot be triggered > for the message content. Although the sender endeavours to maintain a > computer virus-free network, the sender does not warrant that this > transmission is virus-free and will not be liable for any damages resulting > from any virus transmitted.!!!" > > > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ !!!************************************************************************************* "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

Sept. 14, 2016

Re: [Pharo-dev] [ANN] Regular tech hangouts every month

by Max Leske

Cool! Thanks Esteban. > On 14 Sep 2016, at 14:50, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > > Last board meeting we decided to take some actions to improve communication and one of the ideas we had is to start some regular meetings each month, to talk about current release development issues. > > Since Iâm the one who will do it, I decided: > > - I will handle those meetings every last Tuesday of every month at 16h UTC (So people from America-The-Continent can joinâ¦ Yes, is a continent, not a country) > - I will send main topic one week earlier (but it will be an open QA/brainstorm session). > - You can send me topics you want to discuss anytime > - I will *invite* (I mean: force) relevant people for topics to talk (for example, Denis to talk about remote debugging, Pavel/Guille/Christophe about bootstrap) > > I still do not know the medium: > - terf? problem is that a) everybody needs to install a client (is not heavy, but I think there is no linux client) and b) I still donât know how the thing works ;) (but it would be cool to use a smalltalk app). > - hangouts? Iâm fed up with the 10 limitâ¦ we (the consortium) are willing to pay some (not *much*, but some) to have better sessions (we need them also for consortium meetings who always runs out of slots). > - other? > > Well, I will sort out this before the meeting :) > > Anywayâ¦ next tech meeting will beâ¦ (suspenseâ¦)â¦ > > Tuesday 27 September 16h UTC > > cheers, > Esteban

Sept. 14, 2016

Re: [Pharo-dev] [Pharo-users] [ANN] RProjectConnector V2.1

by Serge Stinckwich

Hi Vincent, Ok I try again with the latest Pharo 6.0. When I evaluate: Gofer it smalltalkhubUser: 'VincentBlondeau' project: 'RProjectConnector'; configuration; loadStable There is an error : could not resolve Rconnector. Apparently there is a problem with the package name, because this vincentBlondeau and not VincentBlondeau (Uppercase). Did you already try your configuration in an empty Pharo 6.0 image ? :-) I was able to load RConnector-vincentBlondeau.72 directly from Monticello repo. I modify the RLibrary>>macModuleName path name to /usr/local/Cellar/r/3.3.1_2/R.framework/Versions/3.3/Resources/lib/libR.dylib When I relaunch my image, I have an error: the R session is not well initialized at startup. In RSession>>isExistsRf_initEmbeddedR I still see a reference to Alien class. You are still using Alien ? On Tue, Sep 13, 2016 at 6:25 PM, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > > > >> -----Message d'origine----- >> De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de >> Serge Stinckwich >> EnvoyÃ© : vendredi 2 septembre 2016 16:44 >> Ã : Pharo Development List >> Cc : scismalltalk(a)googlegroups.com; Any question about pharo is welcome >> Objet : Re: [Pharo-dev] [ANN] RProjectConnector V2.1 >> >> Great job Vincent ! >> > It will be great when it will work on OS X ;) > >> There is some problems on Mac OS X: >> - when I try to load in a fresh Pharo 5.0 image, I got a DNU on: >> RObjectArray class>>initElementType: >> I was able to load the package after a while by loading directly the package >> with the Monticello Browser > > Strange, I deleted these methods... Please ensure you are using a Pharo 6.0 image (it should work under Pharo 5.0 too) and that version 14 of ConfigurationOfRProjectConnector and version 71 of the RConnector packages are loaded. > >> - Apparently there is still some methods using NB like: RSession >> class>>checkSession or RSession class>>initEmbeddedR: > > Should not, it is modified ... > >> >> I try to move the R dll close to my Pharo VM and also inside the Plugins >> directory but without success ... > > It should be at the same location that libcairo.2.dylib > >> Is there a way to say where are the R dll instead of copying them ? >> > Didn't think so .. Maybe the VM developers knows ? > > > Thanks! > > Vincent > > >> Thank you. >> >> >> >> >> On Thu, Sep 1, 2016 at 5:42 PM, Blondeau Vincent >> <vincent.blondeau(a)worldline.com> wrote: >> > Hello everyone, >> > >> > >> > >> > I am glad to announce the release of version 2.1 of the RProjectConnector. >> > >> > The binding between Pharo and R (https://www.r-project.org/) is now >> > translated to UFFI and so to Pharo 6.0. >> > >> > >> > >> > You can call directly your R methods from Pharo. For example, with the >> > famous iris clustering example: >> > >> > >> > >> > iris := 'eval' asREval: {RObject findVar: 'iris'}. >> > >> > 'plot' >> > >> > asREval: >> > >> > {(iris at: 'Petal.Length'). >> > >> > (iris at: 'Petal.Width'). >> > >> > (#pch -> 21). >> > >> > (#xlab -> 'length'). >> > >> > (#ylab -> 'Width'). >> > >> > (#bg ->((iris at: 'Species') collect: >> > [ :value | {'red'. 'green3'. 'blue'} at: value ])). >> > >> > (#main -> 'Edgar Anderson''s Iris Data')}. >> > >> > iris inspect. >> > >> > >> > >> > To use it, you should install R and copy the R libraries near the >> > Pharo VM (see the documentation on SmalltalkHub >> > (http://smalltalkhub.com/#!/~VincentBlondeau/RProjectConnector) for >> > how to proceed). >> > >> > >> > >> > Donât forget to relaunch Pharo after the installation to be able to >> > use the connector. >> > >> > >> > >> > Only basic features are implemented yet, but you can participate to >> > its extension! >> > >> > >> > >> > Cheers, >> > >> > Vincent Blondeau >> > >> > >> > >> !!!************************************************************ >> ******* >> > ****************** "Ce message et les piÃ¨ces jointes sont >> > confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il >> > peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous >> > recevez ce message par erreur, merci d'en avertir immÃ©diatement >> > l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre >> > assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre >> > recherchÃ©e quant au contenu de ce message. Bien que les meilleurs >> > efforts soient faits pour maintenir cette transmission exempte de tout >> > virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa >> > responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant >> > d'un virus transmis. >> > >> > This e-mail and the documents attached are confidential and intended >> > solely for the addressee; it may also be privileged. If you receive >> > this e-mail in error, please notify the sender immediately and destroy >> > it. As its integrity cannot be secured on the Internet, the Worldline >> > liability cannot be triggered for the message content. Although the >> > sender endeavours to maintain a computer virus-free network, the >> > sender does not warrant that this transmission is virus-free and will >> > not be liable for any damages resulting from any virus transmitted.!!!" >> >> >> >> -- >> Serge Stinckwich >> UCBN & UMI UMMISCO 209 (IRD/UPMC) >> Every DSL ends up being Smalltalk >> http://www.doesnotunderstand.org/ > > > !!!************************************************************************************* > "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. > > This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!" -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Sept. 14, 2016

[ANN] Regular tech hangouts every month

by Esteban Lorenzano

Hi, Last board meeting we decided to take some actions to improve communication and one of the ideas we had is to start some regular meetings each month, to talk about current release development issues. Since Iâm the one who will do it, I decided: - I will handle those meetings every last Tuesday of every month at 16h UTC (So people from America-The-Continent can joinâ¦ Yes, is a continent, not a country) - I will send main topic one week earlier (but it will be an open QA/brainstorm session). - You can send me topics you want to discuss anytime - I will *invite* (I mean: force) relevant people for topics to talk (for example, Denis to talk about remote debugging, Pavel/Guille/Christophe about bootstrap) I still do not know the medium: - terf? problem is that a) everybody needs to install a client (is not heavy, but I think there is no linux client) and b) I still donât know how the thing works ;) (but it would be cool to use a smalltalk app). - hangouts? Iâm fed up with the 10 limitâ¦ we (the consortium) are willing to pay some (not *much*, but some) to have better sessions (we need them also for consortium meetings who always runs out of slots). - other? Well, I will sort out this before the meeting :) Anywayâ¦ next tech meeting will beâ¦ (suspenseâ¦)â¦ Tuesday 27 September 16h UTC cheers, Esteban

Sept. 14, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60221 Home: https://github.com/pharo-project/pharo-core

Sept. 14, 2016

[pharo-project/pharo-core] 24f358: 60221

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 24f358d5f31ab615454e0bbd7f82ca0f0bb47758 https://github.com/pharo-project/pharo-core/commit/24f358d5f31ab615454e0bbd… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-09-14 (Wed, 14 Sep 2016) Changed paths: M Kernel-Tests.package/ProcessSpecificTest.class/instance/testing/testInheritingExecutionEnvironment.st M Nautilus.package/AbstractNautilusUI.class/instance/build ui buttons/buildBrowseVariablesButton.st M Nautilus.package/AbstractNautilusUI.class/instance/buttons behavior/browseVariableReferences.st M Refactoring-Tests-Environment.package/RBBrowserEnvironmentTest.class/instance/testing-environments/testAndEnvironment.st M SUnit-Core.package/TestExecutionEnvironment.class/instance/initialization/initialize.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60220.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60221.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60220.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60221.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60221 19087 Tracking of processes during test run should not keep processes strongly. https://pharo.fogbugz.com/f/cases/19087 18755 Variable-button raises "SubscriptOutOfBounds: 1" when a Trait is selected https://pharo.fogbugz.com/f/cases/18755 17543 VM crash in Windows when compiling many symbols https://pharo.fogbugz.com/f/cases/17543 http://files.pharo.org/image/60/60221.zip

Sept. 14, 2016

Re: [Pharo-dev] [Pharo 6] failing tests down to 6

by Ben Coman

Cool to hear this progress. cheers -ben On Wed, Sep 14, 2016 at 1:51 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> With these, we are down to 9 failing tests on the CI: >> > We are down to 6! These: > > > SmalllintManifestCheckerTest.testCriticsOf > SmalllintManifestCheckerTest.testToDoOf > - tests need to be updated, will be fixed with next QA update > > ReleaseTest.testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits > - fixed upstream > > SystemAnnouncerLiveTest.testNoDeadSubscriptions > Announcements.Tests.Core.Tests.WeakAnnouncerTest.testNoDeadWeakSubscriptions > > ClassDescriptionTest.testClassDescriptionRespectsPolymorphismWithTraitDescription > #iconNamed: in ClassDescription. > > > >

Sept. 13, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

by Nicolai Hess

2016-09-13 21:00 GMT+02:00 stepharo <stepharo(a)free.fr>: > Hi nicolai > > Why we should not accept > > foo > <func: (3+4) res:0> > ^ self > > and be forced to put around '' > > foo > < func: '(3+4)' res: 0 > > ^ self > > I understand that we store literal but why you do not like it :). > First of all, the old compiler did not accept this. And I am a bit sensitive about changes, we allow a different syntax just because RB happens to allow this (and maybe no one knows why or it just does not happens on purpose). And another reason, even without my fix, if we don't put quotes around that expression, the reformatting the source will convert this to: foo <func: #(3 #+ 4) res: 0> ^ self And, even if (3+4) looks like an expression, it is just a list of literals something like this: foo <func: ([[[}}}) res:0> ^ self would be allowed too. But of course this is only my own opinion :) We can change it back and maybe add support for the reformatter to not convert it to the literal array #(3 #+ 4) . nicolai > Stef > > > 60220 >> 19086 do not allow expressions as pragma arguments >> https://pharo.fogbugz.com/f/cases/19086 >> > > >

Sept. 13, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

by stepharo

Hi nicolai Why we should not accept foo <func: (3+4) res:0> ^ self and be forced to put around '' foo < func: '(3+4)' res: 0 > ^ self I understand that we store literal but why you do not like it :). Stef > 60220 > 19086 do not allow expressions as pragma arguments > https://pharo.fogbugz.com/f/cases/19086

Sept. 13, 2016

[Pharo 6] failing tests down to 6

by Marcus Denker

> > With these, we are down to 9 failing tests on the CI: > We are down to 6! These: SmalllintManifestCheckerTest.testCriticsOf SmalllintManifestCheckerTest.testToDoOf - tests need to be updated, will be fixed with next QA update ReleaseTest.testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits - fixed upstream SystemAnnouncerLiveTest.testNoDeadSubscriptions Announcements.Tests.Core.Tests.WeakAnnouncerTest.testNoDeadWeakSubscriptions ClassDescriptionTest.testClassDescriptionRespectsPolymorphismWithTraitDescription #iconNamed: in ClassDescription.

Sept. 13, 2016