Closed velicuvlad closed 2 months ago
@bmeike Spec was update last night so, in short yes. - Test 27. Also, as noted in test 27 description, itself and test 26 can be merged into a single on and this is what I've done in this PR. Now, it might be the case that I chose the wrong exception to throw, so I will be waiting for Pasin's review. IllegalStateArgumentException
I can't find this exact exception, so I've used NSInternalInconsistencyException
Boy I hate these changes....
We had have a long discussion in Slack last week about this. It was a conclusion that we will make it illegal to use the index updater after calling finish. Sorry, I didn't have time to update the test spec after the discussion. For iOS, it's correct to throw NSInternalInconsistencyException.
count()
,valueAtIndex()
,setVector()
,skipVector()
andfinish()
will throw an NSException if the updater is already finished.