Remove Implementations of `FromIterator` and other `From<other_collection>` traits about nodit HOT 4 CLOSED

Also, FromIterator is not supposed to fail and yet it will panic if you feed it an invalid RangeBounds which is quite bad.

from nodit.

Instead I recommend using append_* functions once they land in #7

If you need to build a RangeBounds* from an Iterator I recommend looping through the values with a for loop and inserting the with the intended insert_* method.

from nodit.

The first attempt at a fix in #16 failed as I forgot about all the places in the crate where I use TryFrom<[]>.

I think the best solution her would be to switch over to a new function RangeBoundsMap::from_slice_strict and write variations for the other insert functions also, since the alternative without custom functions would be to manually use insert_*s everywhere in the docs which would be way worse.

from nodit.

An question popped up whilst implementing the from_slice* functions. The from_slice_overwrite doesn't really make any sense! Why would anyone want to convert between a slice of RangeBounds by sequentially overwriting them??? But I guess since it makes everything consistent I will keep it. Consistency is key after all.

from nodit.