-
-
-
-
we've already "rebalanced" coherence once lol
2 replies 0 retweets 2 likes -
Replying to @ManishEarth @yaahc_
1.41 stabilized a change to the coherence rules from an RFC I wrote a year or two back called re-rebalancing coherence (which was named because it loosens rules originating in an RFC called rebalancing coherence)
1 reply 0 retweets 5 likes -
oh yeah I forgot we rerebalanced it too third time's the charm
1 reply 0 retweets 3 likes -
Replying to @ManishEarth @sgrif
Oh no, things are fine, nothing unsound, just annoying that it's like "you can't impl this as one trait for result<t, e> and e because result could impl error in the future.
1 reply 0 retweets 5 likes
Yup, that's the core tradeoff. If we didn't have that restriction, adding any trait implementation to any type would be a major breaking change
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.