On 3/19/18 8:00 PM, ciechowoj wrote:
Digging out and old yet important issue.
Yep, I've run into that.The workarounds suck, and the worst part is that the error is leaking implementation details to the user that have a very unsatisfactory explanation. I get that the reason is solid, but it doesn't look that way when you look at all the other stuff the compiler can handle.
It reminds me of Swift errors that an expression is too complicated for it to figure out.
-Steve
