On 21 janv. 2014, at 17:53, Stephan Eggermont <stephan@stack.nl> wrote:

I tried loading Deltawerken in Pharo 3.0 and noticed
it is now impossible to load code where a class side method is defined named users.

DEUser class>>users
�^self subclassResponsibility

Stephan

I guess it's a consequence of the unification of Class and Trait APIs. Now SomeClass users�must answer an empty collection.

So you experience a name clash between Pharo meta-level and your domain :(

I still think it was a mistake too push that unification that far, i.e having classes responding to trait specific methods and vice-versa.