You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I discovered that inside of several of the methods of BitVector, we are throwing IndexOutOfRangeException. IndexOutOfRangeException is a special exception type in .NET that should only be thrown from the getter of an indexer. In virtually all other cases, these should be converted to ArgumentOutOfRangeException. Looks like there are a handful of other types that are throwing it, as well. We should ... convert these to ArgumentOutOfRangeException and double-check that there will be no adverse effects from making the change. These were originally intentionally normalized to IndexOutOfRangeException to make the error handling simpler, but since then we have fixed the error handling to catch either IndexOutOfRangeException or ArgumentOutOfRangeException and treat them the same using the IsIndexOutOfBoundsException() extension method (although, it may not be used everywhere it is needed to make the change).
Originally posted by @NightOwl888 in #1018 (comment)
The text was updated successfully, but these errors were encountered: