For example in Spec’s ListModel there is a thing called displayBlock:. And I have to write `list displayBlock: [ :package | package name ]`, while I think that `list displayBlock: #name` is clear enough, but the block receives #cull:cull:
Uko On 19 Jun 2014, at 13:52, Sven Van Caekenberghe <[email protected]> wrote: > I believe this was already discussed long ago, with a decision not to go > further that #cull: (or #value:) on Symbol, some even find that too much from > a design perspective. > > I like writing code like > > #(1 2 3) collect: #asString > > especially interactively, since it is less verbose. > > In what situation did you encounter a need to add #cull:cull: to Symbol ? > > On 19 Jun 2014, at 13:42, Yuriy Tymchuk <[email protected]> wrote: > >> Hi, >> >> maybe we should implement #cull:cull: in symbol so that it will call #cull:? >> Because this looks correct, if block has 1 parameter, then #cull:cull: boils >> down to #value:, but when we have a symbol instead, we have an exception. >> >> I can open an issue and implement that stuff, but I want a feedback from the >> conceptual point of view. >> >> Uko >> > >
