You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 2, 2019. It is now read-only.
In this definition, I'm attempting to show the inductive character of Sg(A, X) i.e. theorem 1.14 in Cliff Bergman's book. This involves inspecting a sequence of elements in X along with evidence that they are members of Y to determine n such that each element is in X n. This apparently requires elimination from Prop to Type, which is verboten; @williamdemeo might remember a similar situation involving the recovery of the preimage of a function from its image.
Basically, this all comes down to the standard library committing to Prop in certain places when really they should be using Sort and let the user declare proof irrelevance at their leisure.
Should we refactor the codebase to work with Sort, use choice, or do something else?
The text was updated successfully, but these errors were encountered:
Seems to me we want Sort. It would be nice if we could do this all (or most of it) constructively, and avoid choice, but I'm not sure whether this is possible or realistic.
In this definition, I'm attempting to show the inductive character of Sg(A, X) i.e. theorem 1.14 in Cliff Bergman's book. This involves inspecting a sequence of elements in
X
along with evidence that they are members ofY
to determinen
such that each element is inX n
. This apparently requires elimination fromProp
toType
, which is verboten; @williamdemeo might remember a similar situation involving the recovery of the preimage of a function from its image.Basically, this all comes down to the standard library committing to
Prop
in certain places when really they should be usingSort
and let the user declare proof irrelevance at their leisure.Should we refactor the codebase to work with
Sort
, usechoice
, or do something else?The text was updated successfully, but these errors were encountered: