About wrap and neighbors

[Ducasse]

It would be nice

• to have neighbour accesses from a location.
• with or not wrapping at edges

This would ease little game building such as miner.

[privat]

for basic wrapping (and pinning, as in SequenceableCollection>>#atPin:, why limiting ourselves), the API question is should we just duplicate (or tri-plicate) all the *at* methods? E.g. atWrap:, atWrap:put:, atColumnWrap:, atWrapX:y:, etc.?
This feels bad :(

Maybe use a combination of methods? So the wrapping can be done by a helper method? e.g. anArray2D at: (anArray2D wrap: aPoint) or anArray2D atColumn: (anArray2D wrapX: aNumber)
This reduces the number of method and could be useful anyway, but it's not fluent...

Or an instance flag that defines the wrapping/pining policy. e.g. anArray2D wrapMode: true; at: aPoint. In fact, I really do not like this one.

[Ducasse]

I should check what atPin: is doing (currently flu so brain slow).

[Ducasse]

About the atWrap: it looks ok for me :). Because this is different API. We could have

a2d wrapAtRow
a2d at:put: 

but this means that the logic will have to check everything. So I agree with you that I do not like it.