The “Swifty” way of doing such a thing is to have the types you care about conform to a protocol that clearly defines the API you’re trying to expose. For example:
If you replace “conjunction” by “O(n) search with early-exit on failure” and “disjunction” by just “O(n) search”, you’ll see why this can lead to computationally painful systems of constraints. Each disjunctive constraint may further contain or create disjunctions ad nauseum, each time incrementing the exponent in the worst-case time it takes to solve the system. Introduction of disjunction into an already complex system (say, one that supports constrained parametric polymorphism and subtyping AND disjunctions through overloads) makes an already difficult problem even harder.
~Robert Widmann
2018/01/13 4:45、Daryle Walker via swift-evolution <swift-evolution@swift.org>のメール: