[swift-evolution] Proposal: change infix operator attributes syntax to be more consistent with the rest of the language
daniel at duan.org
Tue Mar 8 16:03:43 CST 2016
> Joe Groff via swift-evolution <swift-evolution at ...> writes:
> For one, modeling relative precedence using a global integer table is bad
> and opaque, and not every operator makes sense to compose with every other.
If I'm understanding your first point correctly, the precedence will form a DAG
and we use reachability to determine whether two operators have a valid
relationship. That seems pretty straight forward.
> Second, we don't handle operator conflicts between modules very well at
> all, giving essentially impossible-to-resolve conflict errors.
Name mangling might help here?
> > On Mar 5, 2016, at 8:54 PM, Kevin Lundberg via swift-evolution
> > <swift-evolution <at> swift.org> wrote:
More information about the swift-evolution