[core] Correcting discrepancies between `current_transform()` and `matches`
Open
bug
enhancement
- Dominant language
- C++
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Jess has been working on a new match display. Thanks to her work, we've discovered a number of bugs in how matches work right now. Due to the way `iterate` works, `matches` is usually one iteration behind `current_transform()` (except right after `begin()`) and thus functions like `calculate_cost()` are technically wrong. I don't know the best way to correct this right now, but it needs to happen.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.