-
Notifications
You must be signed in to change notification settings - Fork 107
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
remove emit-event shim #1168
remove emit-event shim #1168
Conversation
@@ -1654,7 +1654,7 @@ prettyTerm ty = \case | |||
MkPactGuard name -> parensSep ["create-pact-guard", pretty name] | |||
MkUserGuard g t -> parensSep ["create-user-guard", pretty g, pretty t] | |||
MkModuleGuard name -> parensSep ["create-module-guard", pretty name] | |||
MkCapabilityGuard (Capability _ n) as isPact -> parensSep | |||
MkCapabilityGuard (Capability _ n _) as isPact -> parensSep |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does CapAnnot
not want to be included in the pretty-printed Capability
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If a cap is @managed
or @event
makes no difference here. I think the name should be enough. @jmcardon what do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think a cap being managed should display somehow. Event is something that will someday be replaced by defevent
, I believe.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks great to me.
No description provided.