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

'Wrong' symbol for negated equality in Data.Rational.Unnormalised.* #2114

Closed
jamesmckinna opened this issue Sep 29, 2023 · 7 comments · Fixed by #2118
Closed

'Wrong' symbol for negated equality in Data.Rational.Unnormalised.* #2114

jamesmckinna opened this issue Sep 29, 2023 · 7 comments · Fixed by #2118
Labels

Comments

@jamesmckinna
Copy link
Contributor

The Base module introduces an ad hoc notation _≠_ for the negated equality in the setoid (ℚᵘ, _≃_) .
But there is now no reason to:

@MatthewDaggitt
Copy link
Contributor

So you'd propose to deprecate it in favour of _≄_?

@jamesmckinna
Copy link
Contributor Author

Yes, I think so. It perhaps falls under a bikeshedding label, if we had one, but it seems like an avoidable wart in the 'fresh start' that (I think?) we want v2.0 to be... what's your view?

@JacquesCarette
Copy link
Contributor

This seems quite sensible - using disparate symbols is confusing.

@jamesmckinna
Copy link
Contributor Author

So there is a tension here (for me) between the 'formalistic' choice (take the formally negated symbol), and the 'semantic' choice (the negated equality is, in fact, a tight apartness relation, so that the rationals form a HeytingField, so a suitable choice would be _#_ for an apartness relation). For me, formal beats semantic, but in the interests of discussion...

@JacquesCarette
Copy link
Contributor

Hmm, wouldn't proving that it is a tight apartness relation satisfy the semanticist in you? i.e. you first name the concept with the 'obvious' name, and then show that it has quite a bit more structure than naively expected. So then if you want to use it as an apartness relation, you can do it via using the HeytingField bundle, thus regaining the 'right' name?

@jamesmckinna
Copy link
Contributor Author

(I think so, but all those various parts of me are at present exploding in all directions...)

@jamesmckinna
Copy link
Contributor Author

And, regarding the deprecation, I think that the symbol should arise by suitably renaming the default negated-equality introduced by Setoid... but perhaps those dependencies don't quite cash out the way I might hope?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants