If you tested it, there's a problem with the current behavior independent of associated type inference, and it should be fixed whether or not the proposal is accepted.
> On Jun 28, 2016, at 10:47 PM, Paulo Faria <pa...@zewo.io> wrote: > > >> On Jun 29, 2016, at 2:28 AM, Austin Zheng <austinzh...@gmail.com >> <mailto:austinzh...@gmail.com>> wrote: >> >> I'm not sure this is a problem. Once you bind the associated types >> explicitly, the requirements using those associated types need to match the >> bound types otherwise the type checker will emit an error. If you have >> default associated types and default implementations, but then bind the >> associated types differently and do not update your type-specific >> implementations to use those other types, you will get an error message. >> This is how explicitly specifying associated types works today. >> >> Austin > > The problem is that it doesn’t give me any error message. I tested it. > > >
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
