- Pharo-dev - lists.pharo.org

This week (20/2022) on the Pharo Issue Tracker

by Marcus Denker

We merged 10 PRs and closed 9 Issues: Image Size ========== - Reset SelectorTable on #cleanUp #11235 https://github.com/pharo-project/pharo/pull/11235 Clean Blocks ============ - CleanBlock-Hierachy-Cleanup #11225 https://github.com/pharo-project/pharo/pull/11225 - 11218-CleanBlocks-Compiler-should-not-change-the-outerCode-for-all-blocks-in-the-literals #11229 https://github.com/pharo-project/pharo/pull/11229 Fixes ===== - OneCharacterSymbols: Symbol allSymbols contains one-character symbols twice #11241 https://github.com/pharo-project/pharo/pull/11241 - Revert "FIX issue #10933: Scaled decimals comparison result depends on the number creation method" #11228 https://github.com/pharo-project/pharo/pull/11228 - Fix an issue where streaming client usage failed when the server set a connection close. #11214 https://github.com/pharo-project/pharo/pull/11214 - Porting fixes from Pharo 10 to Pharo 11 #11207 https://github.com/pharo-project/pharo/pull/11207 Forward port to Pharo11: Allow to serialize Memory File Systems #11116 #11122 Forward port Pharo11: Fix #isPrime when sent to 3. #11154 Cleanup ======= - 11230-ClassParser-Improve-Hierarchy-CDSharedVariableNodeCDSlotNode #11231 https://github.com/pharo-project/pharo/pull/11231 - Categorize-Uncategorized-IceTipSpPresenter #1585 https://github.com/pharo-vcs/iceberg/pull/1585

May 20, 2022

PhEP submitted: String interpolation for Pharo

by Esteban Lorenzano

Hello, There is a new PhEP (Pharo Enhancement Proposal) submitted titled: "String interpolation for Pharo" that requires the attention of the community: https://github.com/pharo-project/pheps/pull/9 Cheers! Esteban

May 19, 2022

[Review needed] Symbol allSymbols contains one-character symbols twice #11242

by Marcus Denker

Symbol allSymbols asBag occurrencesOf: #a allSymbols returns an array of all symbols. The reason it contains #a twice: There is OneCharacterSymbols. - it is initialized with: OneCharacterSymbols := (1 to: 256) collect: [ :i | (i - 1) asCharacter asSymbol]. the #asSymbol puts the OneCharacterSymbols in the main symbol table already. Then OneCharacterSymbols is just used by #allSymbols and #selectorsContaining:, with the latter having no users. https://github.com/pharo-project/pharo/pull/11241 Besides the bugfix, it removes some one Character symbols that never got used and speeds up #allSymbols a little. And it simplifies the code related to the symbol table a little, which will make it easier to improve it later. Marcus

May 19, 2022

Re: Please check older Issue tracker entries!

by Sebastian Jordan Montano

Yes, thank you Marcus! Sebastian Jordan ----- Mail original ----- > De: "serge stinckwich" <serge.stinckwich(a)gmail.com> > Ã: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Cc: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> > EnvoyÃ©: Mercredi 18 Mai 2022 11:51:30 > Objet: [Pharo-dev] Re: Please check older Issue tracker entries! > Thank you Marcus for your effort to engage more people from the community on > managing the issue tracker entries more efficiently ð > Regards, > > Sent from my iPhone > >> On 18 May 2022, at 14:50, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> ï»¿Hi, >> >> One problem with a public issue tracker: it accumulates lots of issuesâ¦ >> >> This sadly means that issues will not be looked at one by oneâ¦ there are >> just too many. >> >> One thing that is interesting to do is to check the issue that *you* submitted. >> >> - Is the issue still relevant? >> - is the title good and in sync with the issue? >> - Has it been fixed already ? (it happens!) >> >> Then, for every issue there is a ânext stepâ. It can be a good thing to spell >> out >> very explicitly what the next step is âWe need to create a Pull Request for the >> suggested fixâ. >> >> Or maybe what is needed is a summary of the huge discussion in the >> issue tracker entry. >> >> Another idea: try to find others to help. E.g. >> >> - send a mail to the mailinglist. >> - ask on discord. >> >> Maybe you can find a small group that works on this issue together. >> >> >> >> Marcus >> >>

May 18, 2022

unsubscibe

by dhz＠zh.com

unsubscibe

May 18, 2022

Re: Please check older Issue tracker entries!

by serge.stinckwich＠gmail.com

Thank you Marcus for your effort to engage more people from the community on managing the issue tracker entries more efficiently ð Regards, Sent from my iPhone > On 18 May 2022, at 14:50, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > ï»¿Hi, > > One problem with a public issue tracker: it accumulates lots of issuesâ¦ > > This sadly means that issues will not be looked at one by oneâ¦ there are > just too many. > > One thing that is interesting to do is to check the issue that *you* submitted. > > - Is the issue still relevant? > - is the title good and in sync with the issue? > - Has it been fixed already ? (it happens!) > > Then, for every issue there is a ânext stepâ. It can be a good thing to spell out > very explicitly what the next step is âWe need to create a Pull Request for the > suggested fixâ. > > Or maybe what is needed is a summary of the huge discussion in the > issue tracker entry. > > Another idea: try to find others to help. E.g. > > - send a mail to the mailinglist. > - ask on discord. > > Maybe you can find a small group that works on this issue together. > > > > Marcus > > >

May 18, 2022

Please check older Issue tracker entries!

by Marcus Denker

Hi, One problem with a public issue tracker: it accumulates lots of issuesâ¦ This sadly means that issues will not be looked at one by oneâ¦ there are just too many. One thing that is interesting to do is to check the issue that *you* submitted. - Is the issue still relevant? - is the title good and in sync with the issue? - Has it been fixed already ? (it happens!) Then, for every issue there is a ânext stepâ. It can be a good thing to spell out very explicitly what the next step is âWe need to create a Pull Request for the suggested fixâ. Or maybe what is needed is a summary of the huge discussion in the issue tracker entry. Another idea: try to find others to help. E.g. - send a mail to the mailinglist. - ask on discord. Maybe you can find a small group that works on this issue together. Marcus

May 18, 2022

ANN: Introducing PhEPs (Pharo Enhancement Proposals)

by Esteban Lorenzano

Hello, Some of you were present at PharoDays 2022 were we made a presentation explaining this new way of handling the evolution of Pharo. In that talk we explained that this is an attempt of having the community involved in more deep way, with a clear (and visible) decision process, taking the model the Python community has been using with success (so why not us? :P). In a nutshell, the idea is that everybody wanting to work on any kind of enhancement for Pharo can now send their proposal and start a discussion process (a discussion arbitrated by the Pharo Board), and if this discussion leads to an accepted enhancement, the work will be integrated as part of the Pharo Environment. How it works? - There is a repository: https://github.com/pharo-project/pheps - and a detailed description of the process: https://github.com/pharo-project/pheps/blob/main/phep-0001.md You will have all the information you need there, but here is a summary of the process (you can also find it in the guidelines PhEP): 0. (Optional, but recommended) the proposer discusses the idea in pharo-dev list or discord, with members of the team, and gather ideas. 1. The proposer will clone the PhEP repository (pharo-project/pheps) and adds a proposal draft following the required stucture: - the file will not have an ID, hence it needs to be called `phep-proposal.md` - the proposal will have the header and structure explained in the section **Submitting a PhEP** (header, abstract, motivation and description). - the proposal will also have a "champion" (which by default is the author itself), responsible for the implementation of the proposal in case is been accepted. 2. The proposal will be submitted as PR to the PhEP repository. 3. A mail will be send to `pharo-dev` mailing list, including the link and the abstract of the proposal. 4. There will be a discussion process and in case of acceptance of the proposal, an ID will be assigned by the reviewer. 5. As final stage, the author renames the `phep-proposal.md` file as `phep-ID.md` and includes the ID in the phep file header (this step can be performed by the reviewer if he decides so). 6. The reviewer will merge the PR In the next days I will be sending a couple fo PhEPs to add to those already there, to get the process started. Do not hesitate to participate! Cheers, Esteban ps: Yes, I am aware "pheps" sounds fun on english :)

May 17, 2022

[review needed] Better structure for CleanBlock Hierachy

by Marcus Denker

Hi, For now, CleanBlockClosure was a subclass of FullBlockClosure, which is not nice (as CleanBlockClosure is not a FullBlockClosure) The PR https://github.com/pharo-project/pharo/pull/11225 improves that a bit: â¢ make CleanBlockClosure a subclass of BlockClosure â¢ BlockClosure is now tagged abstract â¢ override #receiver in CleanBlockClosure â¢ push down #sender â¢ Improve comments ( fixes Check BlockClosure comments for mention of startpc #11217 ) Both CleanBlockClosure and FullBlockClosure add the ivar âreceiverâ, as the vm needs it (it is nil for CleanBlockClosure). This we should look at that later. e.g. have it defined in BlockClosure once, but that has to be done as itâs own PR as it is not a change doable from the image. The change should be save to merge, as CleanBlockClosure is, for now, just used in the tests that turn it on explicitly. PR for review: https://github.com/pharo-project/pharo/pull/11225 Marcus

May 17, 2022

Consider watching the GitHub repo

by Marcus Denker

Hi, GitHub creates a kind of âspontaneous mini mailinglistsâ for every issue and every PR. For one, this is nice as all the discussion is at one place and can be found easily, and it makes sure those who are involved in the issue get the messages (e.g. the one who created an issue tracker entry). But: you will only see those by default. If you want to get an impression of things happening, it might be interesting to âWatchâ the repository. You can do that by clicking on the âWatchâ button on https://github.com/pharo-project/pharo Marcus

May 16, 2022