Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
stdpp
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Monitor
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Iris
stdpp
Merge requests
!500
explain why we don't have 'ge' notation
Code
Review changes
Check out branch
Download
Patches
Plain diff
Merged
explain why we don't have 'ge' notation
ralf/ge
into
master
Overview
2
Commits
2
Pipelines
3
Changes
1
All threads resolved!
Show all comments
Merged
Ralf Jung
requested to merge
ralf/ge
into
master
1 year ago
Overview
2
Commits
2
Pipelines
3
Changes
1
All threads resolved!
Show all comments
Expand
This came up in
!499 (closed)
0
0
Merge request reports
Compare
master
version 2
7286a3cf
1 year ago
version 1
a03f158e
1 year ago
master (base)
and
latest version
latest version
93177374
2 commits,
1 year ago
version 2
7286a3cf
1 commit,
1 year ago
version 1
a03f158e
1 commit,
1 year ago
1 file
+
15
−
0
Inline
Compare changes
Side-by-side
Inline
Show whitespace changes
Show one file at a time
stdpp/numbers.v
+
15
−
0
Options
@@ -46,6 +46,21 @@ Reserved Notation "x ≤ y ≤ z ≤ z'"
(
at
level
70
,
y
at
next
level
,
z
at
next
level
)
.
Infix
"≤"
:=
le
:
nat_scope
.
(** We do *not* add notation for [≥] mapping to [ge], and we do also not use the
[>] notation from the Coq standard library. Using such notations leads to
annoying problems: if you have [x < y] in the context and need [y > x] for some
lemma, [assumption] won't work because [x < y] and [y > x] are not
definitionally equal. It is just generally frustrating to deal with this
mismatch, and much preferable to state logically equivalent things in syntactically
equal ways.
As an alternative, we could define [>] and [≥] as [parsing only] notation that
maps to [<] and [≤], respectively (similar to math-comp). This would change the
notation for [<] from the Coq standard library to something that is not
definitionally equal, so we avoid that as well.
This concern applies to all number types: [nat], [N], [Z], [positive], [Qc] and
[Qp]. *)
Notation
"x ≤ y ≤ z"
:=
(
x
≤
y
∧
y
≤
z
)
%
nat
:
nat_scope
.
Notation
"x ≤ y < z"
:=
(
x
≤
y
∧
y
<
z
)
%
nat
:
nat_scope
.
Notation
"x < y ≤ z"
:=
(
x
<
y
∧
y
≤
z
)
%
nat
:
nat_scope
.
Loading