Skip to content

Correcting the definition of noccur_between in Template – main branch #2771

Correcting the definition of noccur_between in Template – main branch

Correcting the definition of noccur_between in Template – main branch #2771

Triggered via pull request May 23, 2024 15:07
Status Success
Total duration 35m 22s
Artifacts

build.yml

on: pull_request
checktodos
3s
checktodos
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

40 warnings
build (dev, 4.14-flambda, local)
Notation "_ =1 _" was already used in scope type_scope.
build (dev, 4.14-flambda, local)
Notation "_ =2 _" was already used in scope type_scope.
build (dev, 4.14-flambda, local)
Overwriting previous delimiting key B in scope bool_scope
build (dev, 4.14-flambda, local)
Notation "_ =1 _" was already used in scope type_scope.
build (dev, 4.14-flambda, local)
Notation "_ =2 _" was already used in scope type_scope.
build (dev, 4.14-flambda, local)
Notation "_ =1 _" was already used in scope type_scope.
build (dev, 4.14-flambda, local)
Notation "_ =2 _" was already used in scope type_scope.
build (dev, 4.14-flambda, local)
Using Vector.t is known to be technically difficult, see
build (dev, 4.14-flambda, local)
Using Vector.t is known to be technically difficult, see
build (dev, 4.14-flambda, local)
The following logical axioms were
build (dev, 4.14-flambda, opam)
Notation "_ =1 _" was already used in scope type_scope.
build (dev, 4.14-flambda, opam)
Notation "_ =2 _" was already used in scope type_scope.
build (dev, 4.14-flambda, opam)
Notation "_ =1 _" was already used in scope type_scope.
build (dev, 4.14-flambda, opam)
Notation "_ =2 _" was already used in scope type_scope.
build (dev, 4.14-flambda, opam)
Overwriting previous delimiting key B in scope bool_scope
build (dev, 4.14-flambda, opam)
Using Vector.t is known to be technically difficult, see
build (dev, 4.14-flambda, opam)
Notation "_ =1 _" was already used in scope type_scope.
build (dev, 4.14-flambda, opam)
Notation "_ =2 _" was already used in scope type_scope.
build (dev, 4.14-flambda, opam)
Using Vector.t is known to be technically difficult, see
build (dev, 4.14-flambda, opam)
The following logical axioms were
build (dev, 4.09-flambda, local)
Notation "_ =1 _" was already used in scope type_scope.
build (dev, 4.09-flambda, local)
Notation "_ =2 _" was already used in scope type_scope.
build (dev, 4.09-flambda, local)
Overwriting previous delimiting key B in scope bool_scope
build (dev, 4.09-flambda, local)
Notation "_ =1 _" was already used in scope type_scope.
build (dev, 4.09-flambda, local)
Notation "_ =2 _" was already used in scope type_scope.
build (dev, 4.09-flambda, local)
Notation "_ =1 _" was already used in scope type_scope.
build (dev, 4.09-flambda, local)
Notation "_ =2 _" was already used in scope type_scope.
build (dev, 4.09-flambda, local)
Using Vector.t is known to be technically difficult, see
build (dev, 4.09-flambda, local)
Using Vector.t is known to be technically difficult, see
build (dev, 4.09-flambda, local)
The following logical axioms were
build (dev, 4.09-flambda, opam)
Notation "_ =1 _" was already used in scope type_scope.
build (dev, 4.09-flambda, opam)
Notation "_ =2 _" was already used in scope type_scope.
build (dev, 4.09-flambda, opam)
Notation "_ =1 _" was already used in scope type_scope.
build (dev, 4.09-flambda, opam)
Notation "_ =2 _" was already used in scope type_scope.
build (dev, 4.09-flambda, opam)
Overwriting previous delimiting key B in scope bool_scope
build (dev, 4.09-flambda, opam)
Using Vector.t is known to be technically difficult, see
build (dev, 4.09-flambda, opam)
Notation "_ =1 _" was already used in scope type_scope.
build (dev, 4.09-flambda, opam)
Notation "_ =2 _" was already used in scope type_scope.
build (dev, 4.09-flambda, opam)
Using Vector.t is known to be technically difficult, see
build (dev, 4.09-flambda, opam)
The following logical axioms were