-
Notifications
You must be signed in to change notification settings - Fork 247
Rename excluded-middle
#1856
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
Comments
Two remarks:
|
No reason, and indeed it is about to change imminently in #1855 to what you suggest.
Sure, I would be happy with that. It's not that I'm pro a particular change, it's more that I'm anti the current name 😄 |
On second thoughts about the second... |
@MatthewDaggitt everything moving to fast for me to keep up, even with my own thoughts. Interesting to see/interested in #1855 , will try to catch-up before commenting further. And both Wikipedia and SEP tell me that I am mistaken above. |
The more radical alternative, for those familiar with Grothendieck topologies/ |
No those PRs didn't resolve this issue. |
A bit confused here - does this issue require renaming the actual |
I wonder if we can steal some terminology from Coq? ClassicalFacts might be a reasonable place to start digging. Just in case people's opinions have again drifted. |
I think the current name of
excluded-middle
inRelation.Nullary.Negation
is a bit disingenous. I think¬¬-excluded-middle
would be better.The text was updated successfully, but these errors were encountered: