chore: Use Option.get instead of Options.get
#154
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The implemention of `Option.get` is exactly what was written here.
|
Thanks! There is no CI for this repository: should I simply push the big green button that I learned to fear so much? |
|
There is CI; check out the green check next to my commit! |
|
We don't check anything other than "does the PDF build" at the minute in CI, none of the Lean code actually gets executed (nor does any inline output get checked). All that being said as someone who's merged a bunch of PRs in the repo yes I think be bold and hit the button when comfortable, as otherwise things stagnate. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The implemention of
Option.getis exactly what was written here.