Re: MV Keys

vc wrote:
> mAsterdam wrote:
>

>>vc wrote:
>>
>>>mAsterdam wrote:
>>>[...]
>>>
>>>
>>>>Extrapolating, ISTM your answer to the question:
>>>>"could this removeAt operation possibly be useful
>>>>in a concurrent environment?" would be
>>>>that it is irrelevant:
>>>>removeAt(index) isn't even valid under concurrency.
>>>>
>>>>Am I understanding your point correctly?
>>>
>>>
>>>No.  The concurrency is irrelevant thanks to the CC's ensuring that the
>>>concurrent execution result is equivalent to some serial execution of
>>>the same transactions.  It does not matter what kind of write
>>>operations you want to have in your database.
>>
>>"The concurrency is irrelevant"
>>In this case this goes to say 'It doesn't matter wether
>>there is concurrency or not, the effect of
>>OurSharedList.removeAt(3) is the same.'
>>
>>What should the effect of OurSharedList.removeAt(3) be?

Yep. So what should it be?

> I was objecting to your invoking the ghost of concurrency:
>
> "Aside (the example surely illustrates your point)
> could this removeAt operation possibly be useful
> in a concurrent environment?
> "

I see a difference in the use of indices between a list under single control and a shared list.

> I do not know whether the operation is useful per se, you tell me.

Don't know really. Hmm... try:

The contestants ended on 2nd place ex equo. For the ceremony add a second prize for 2nd place, and remove the third prize (desired effect: 2 silver medals, no bronze medal). Received on Sat Mar 04 2006 - 12:47:36 CST