Re: [Pharo-dev] Refactoring and traits…

But is there an issue or not? Because I was not able to find it. If there is no issue I will create one. Cheers. Uko > On 21 Nov 2015, at 12:15, stepharo wrote: > > > > Le 20/11/15 15:01, Yuriy Tymchuk a écrit : >> Hi guys, >> >> is it a known issue that if you are

Re: [Pharo-dev] Refactoring and traits…

2015-11-23 9:01 GMT+01:00 Yuriy Tymchuk : > But is there an issue or not? Because I was not able to find it. If there > is no issue I will create one. > please create one. There are two other issues about RB and Traits but they don't match this issue - I think > > Cheers.

Re: [Pharo-dev] Refactoring and traits…

Le 20/11/15 15:01, Yuriy Tymchuk a écrit : Hi guys, is it a known issue that if you are refactoring something (eg. doing a class rename) and some changes should happen in a method which comes from trait, then new methods are compiled in concrete classes instead of changing the trait

Re: [Pharo-dev] Refactoring and traits…

Not sure about current Pharo, but I know that it has been a problem in the past (e.g. in 1.3 you should *never* use refactoring when a trait is affected). > On 20 Nov 2015, at 15:01, Yuriy Tymchuk wrote: > > Hi guys, > > is it a known issue that if you are refactoring

[Pharo-dev] Refactoring and traits…

Hi guys, is it a known issue that if you are refactoring something (eg. doing a class rename) and some changes should happen in a method which comes from trait, then new methods are compiled in concrete classes instead of changing the trait method? Cheers. Uko

Re: [Pharo-dev] Refactoring and traits…

Definitely had this (new methods are compiled in concrete classes instead of changing the trait method) several times, although I'm not sure if it was after refactoring, or something else (loading packages?). -- View this message in context: