Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix handling of junctions by Range ACCEPTS
It would manually thread over topic if it's a junction. The default `ACCEPTS` method now expects `Any`-typed topic. Since we don't have `cmp` operator for `Mu`, `Range`, in order to handle any user-created direct `Mu` child, tries to find user-defined `&infix:<cmp>` and throws with `X::Range::Incomparable` if can't find any appropriate. There are still two problems here. First, there is no support for custom user `cmp` operator for `Any`-inheriting classes. Second, custom operator couldn't be found for `Mu`-inheriting classes if they're part of a junction. In the latter case the problem is about the fact that `CLIENT::` namespace would point into `Junction` class. Both issues can only be fixed at the cost of performance loss which is barely acceptable considering the wide use of ranges across the codebase.
- Loading branch information
Showing
2 changed files
with
36 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters