-
Notifications
You must be signed in to change notification settings - Fork 44
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
Warning for inlining Signature for #622
Comments
Well if it inlines it, then it might end up doing so several time, which would be inefficient I think. Hence why it asks the user to derive the signature once and for all? If it could be a quickfix then all would be good no? |
That could work, but why can't Derive NoConfusion = Derive NoConfusion + Signature ? |
My guess would be that this way you know that this is a side effect of |
It but my point is should the user be allowed to derive signature at all ? Shouldn't it be done automatically ? |
A warning
Is triggered when deriving NoConfusionHom but not when deriving NoConfusion.
I would have expected the opposite.
Further, is there even a need for a warning ? I would expect users not to have to derive Signature as it exposes the internal interface which users should not have to care about ?
The text was updated successfully, but these errors were encountered: