11 hours later…
12:14
@LeakyNun Nope they are not. ZFC does not have a notion of "function", and you are free to define it (definitorial expansion) in any way you like as long as you can use it in the ways you want.
Well, currently in my construction attempt exepriment (in another chat room), I have the existence of a universe object as an axiom, I am trying to build some kind of inference rule for membership because I will need to think carefully how to populate this universe so that I won't end up accidentally including objects of null value
"x :· S" denotes "x is of type S or is predicatively null". Here "predicatively null" is supposed to mean "we predicatively know it is null".
This essentially says that if you have a procedure f whose input domain is S and whose output is predicatively known to be either of type T or null, then applying it to any x that is predicatively known to be either of type S or null yields something that is predicatively known to be of type T or null.
12:34
Yes. I always say that my type theory is strongly influenced by the computability viewpoint as well as programming language design.
@ManeeshNarayanan You need at least a 100% grasp of some deductive system for full first-order logic. I would recommend a Fitch-style natural deduction such as this variant. For ordinary mathematics, you often do not need a much deeper understanding of logic, but of course the more you know about logic the better. =)
The reason for my first point is that hard problems often involve many levels of quantifiers, including nested inductions, and you cannot do them properly without a 100% grasp of a deductive system (whether explicit or just in your head).
@Espinoza Sadly, I haven't seen any author that does. I did it consistently throughout the notes I provided for a short optional mathematics course that I taught, so it is definitely doable, but people who have never tried it usually think it is infeasible to write proofs so structurally.
@famesyasd Your this question actually has a trivial answer; you did not use the right definition of derivative when you said "vanishing there". However, there is an extremely interesting question about what what you did means.
Let us be more precise. For ease of understanding, I will use a framework where we analyze variables that vary with a parameter.
Take real parameter t. Let x = sin(t)^3 and y = cos(t)^3. (So x,y are variables that vary with t.) Then everywhere dx/dt = 3·sin(t)^2·cos(t) and dy/dt = −3·cos(t)^2·sin(t). In particular, if t is a multiple of π/2, then dx/dt = dy/dt = 0. This is probably what you were talking about. What does it mean? Well if t is time, then the point (x,y) always moves with a well-defined velocity, which is zero at each cusp (corner), meaning that it comes to a (momentary) stop at that point!
You should also see that you are making a logical error when comparing to dy/dx. In this framework, the chain rule states: Take variables x,y,z varying with parameter t. Whenever dy/dx and dz/dy are both defined, dz/dx = dz/dy · dy/dx.
You definitely cannot apply it here to get dy/dx, because dt/dx is certainly not defined since dx/dt = 0.
It also turns out that when t = 0 we have dx/dy = 0. Proof: As t → 0 we have the following. x ∈ (t+o(t))^3 ⊆ t^3+o(t^3). y ∈ (1−t^2/2+o(t^2))^3 ⊆ 1+t^2·3/2+o(t^2). Thus Δx/Δy ∈ ( t^3+o(t^3) ) / ( t^2·3/2+o(t^2) ) ∈ t+o(t) → 0.
Two notes. Try the same approach for z = sin(t)^2 and w = cos(t)^2, and observe that when t is a multiple of π/2 we also have dx/dt = dy/dt = 0 but now have dx/dy = dy/dx = −1.
« first day (571 days earlier) ← previous day next day → last day (2540 days later) »