Well, Iâm glad I've struck a nerve there :) I agree that signalling an exception isnât wrong, itâs just annoying because you have to do the check manually each time. I think I like #sum:ifEmpty:. When you look through the methods in Collection youâll see #sum, #sum: and #sum:ifEmpty together in one place and it will be clear how to use them.
On 01 Dec 2015, at 12:52, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 01 Dec 2015, at 12:45, Stephan Eggermont <stephan@stack.nl> wrote:
On 01-12-15 11:46, Sven Van Caekenberghe wrote:
The basic question for me is, what should
#() sum
return. Right now, it is an error, I would very much like that for this common case the result would be 0. There is a lot of power (easy of use) in a unary selector, we should not destroy that with semantics that force a test before using it.
I like the error, it aligns with most of our collection protocol.
I hate the error, a lot ;-)
+1
It shows the need for #sum:ifEmpty: though
Yes, as long as #() sum == 0
+100 That allows for nice Smalltalk like âmyNumbers sum isZero â¦â.
I want the simplest case to be simple, having a non-0 default is a special case IMHO
Stephan