Last week I naïvely thought: "let's quickly port the willow-utils path successor functions and get that out of the way". Things did not work out that way!
TL;DR: All path successor implementations up to this point are wrong, and we were only able to find out how using fuzz testing. willow-util's implementations need to be fixed, as it may be generating the wrong ranges for areas.
SubspaceId
Added successor method.
PathComponent trait
Added new_with_tail method
Added empty method
Added try_append_zero_byte method
Added set_byte method
Added try_increment_fixed_width method
Added prefix_successor method
Path trait
The iterator returned by the components method must implement ExactSizeIterator and DoubleEndedIterator
Last week I naïvely thought: "let's quickly port the willow-utils path successor functions and get that out of the way". Things did not work out that way!
TL;DR: All path successor implementations up to this point are wrong, and we were only able to find out how using fuzz testing. willow-util's implementations need to be fixed, as it may be generating the wrong ranges for areas.
SubspaceId
successor
method.PathComponent
traitnew_with_tail
methodempty
methodtry_append_zero_byte
methodset_byte
methodtry_increment_fixed_width
methodprefix_successor
methodPath
traitcomponents
method must implementExactSizeIterator
andDoubleEndedIterator
component_count
methodis_empty
methodis_prefix_of
successor
methodsuccessor_of_prefix
methodOrd
,PartialOrd
Testing
Arbitrary
forPathComponentBox
Arbitrary
forPathRc
Path::successor
Path::successor_of_prefix