I agree this exception should be more specific.
By the way one needs to update all the primitive mutating objects, such as
at:put:, so that when it fails because it attempts to mutate a read-only
object a proper error is raised instead of SubscriptOutOfBounds with an
in-bound index.
Maybe an inte
When I read that, I thought that errorNotIndexable would raise an
Exception different from Error.
But this is not the case and it means that people should write not so good
tests by checking Error
instead of a concrete Exception.
[[[
MyExampleSetTest >> testIllegal
self should: [ empt
