-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MessageBuilder.format_distinctly doesn't make identically named (but different) types distinct when one is generic #3860
Comments
Hmm, it looks like this is handled in the general case, I'm just hitting it because one of the types is generic (and so the string representations are different in the first comparison in Let me update the issue title. |
I started looking at this, but I think it'll be much easier after #3430 has landed. |
Hm, maybe you can help with #3430? That PR seems to have ended up in a bit of quicksand... |
Yep, I'll definitely take a look. |
I thin this one can be fixed now, since the PR superseding #3430 is now merged. |
I don't think it is yet, that work was prerequisite to looking at this.
…On Sat, 2 Sep 2017, 11:42 Ivan Levkivskyi ***@***.***> wrote:
I thin this one can be fixed now, since the PR superseding #3430
<#3430> is now merged.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3860 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAD1ECBYVUsy-_AML0D2ZCfM-iWaxI1sks5seTD4gaJpZM4O_DSk>
.
|
I've been playing around with the plugin interface, and was hitting a strange error with the following (minimal) example plugin:
It took a while of staring confusedly at my code to realise that the fix is quite simple:
It would be good to have a bit more information about where the types come from in this case.
The text was updated successfully, but these errors were encountered: