diff options
author | William Carroll <wpcarro@gmail.com> | 2020-02-08T15·57+0000 |
---|---|---|
committer | William Carroll <wpcarro@gmail.com> | 2020-02-10T10·06+0000 |
commit | 8584059e7cd72656b3e90785c25d2fbb5b350229 (patch) | |
tree | 4a017225a2a197220abdabe29bc81513f3b1ccee /data_structures_and_algorithms/merging-ranges.py | |
parent | f145bc9eb6f1bc51fd70a3df02c978b3333fa012 (diff) |
Support cycle/{append,remove}
Supporting these functions was a little tricky. For example, how should we handle calling cycle/remove on the item that is currently focused? After attempting to be clever, I decided to just set the value to nil and let the consumer decide what is best for them. I can always support a more opinionated version that fallsback to previous-index if previous-index is set. But until I have a better idea of how I'm going to consume this, I think nil is the best option.
Diffstat (limited to 'data_structures_and_algorithms/merging-ranges.py')
0 files changed, 0 insertions, 0 deletions