Skip to content
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

[Merged by Bors] - feat: (↑) notation for coercions #199

Closed
wants to merge 2 commits into from
Closed

Conversation

gebner
Copy link
Member

@gebner gebner commented Feb 21, 2022

See leanprover-community/mathport#116 (comment)

The notation is a bit problematic for the pretty-printer, as it doesn't automatically insert parentheses to disambiguate it from the built-in coercion notation. Alternatives:

  1. Use a different token.
  2. Magically define (↑ ∙) to be the eta-reduction of fun x => ↑x.

PS: the old macro for ↑ x was redundant since it's been moved to core some time ago.

@digama0
Copy link
Member

digama0 commented Feb 21, 2022

You write (↑) in the PR and documentation but it can apparently be used without parentheses. Can we make those required?

@gebner
Copy link
Member Author

gebner commented Feb 21, 2022

That's also a solution. 😄

@gebner
Copy link
Member Author

gebner commented Feb 21, 2022

bors merge

bors bot pushed a commit that referenced this pull request Feb 21, 2022
See leanprover-community/mathport#116 (comment)

The notation is a bit problematic for the pretty-printer, as it doesn't automatically insert parentheses to disambiguate it from the built-in coercion notation.  Alternatives:
 1. Use a different token.
 2. Magically define `(↑ ∙)` to be the eta-reduction of `fun x => ↑x`.

PS: the old macro for `↑ x` was redundant since it's been moved to core some time ago.
@bors
Copy link

bors bot commented Feb 21, 2022

Pull request successfully merged into master.

Build succeeded:

@bors bors bot changed the title feat: (↑) notation for coercions [Merged by Bors] - feat: (↑) notation for coercions Feb 21, 2022
@bors bors bot closed this Feb 21, 2022
@bors bors bot deleted the coeop branch February 21, 2022 14:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants