-
Notifications
You must be signed in to change notification settings - Fork 22
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
function extensionality #20
Comments
Yes, we discussed that and that's why you called it a principle and not an axiom. |
It might be better to move it to the section on equivalences, so we could take that function to be an inverse of the function in the exercise. |
The narrative I tried to follow is: if I introduce a type former, here X->Y, I explain what it "means" that to elements of the newly formed type are equal in terms of equality of the constituent types. This "means" is often modulo an equivalence, and cannot be made precise before the definition of equivalence is in place. Cf. "equivalent" in the last sentence of 5.3. |
Fine with me. But we could give a name to the function in Exc. 2.4.3 and come back to this when we have equivalences. I can make a proposal. |
Done 03739c1 The exercise had to become a definition since we cannot have an axiom depend on how somebody solves the exercise. |
I'm a little dissatisfied with this discussion:
because, a priori, there may be multiple functions of type
( ∏ (x:X), ( f(x) = g(x) )) → f=g
.The text was updated successfully, but these errors were encountered: