Conditional statements
"If... then" claims about a link: whenever the if part happens, the then part does too. One is broken only when the if part is true and the then part false - so a wet street doesn't prove it rained.
Depth 1 · Foundation
You know an if-then claim is broken only when the if part happens without the then part, and that from it "the then part didn't happen" follows backwards but "the then part happened" doesn't.
Sign in to prove what you know with a short quiz, see how deep you've gone, and earn XP for it.
Sign in with GoogleDepths of understanding
- 1
Foundation
You know an if-then claim is broken only when the if part happens without the then part, and that from it "the then part didn't happen" follows backwards but "the then part happened" doesn't.
- 2
Deeper
"If not the then part, then not the if part" (the contrapositive) says the same thing as the original, and the converse doesn't.
Master depth 1 first
Your path here
What's still between you and Conditional statements, depth 1, in the order you can learn it.
Where it fits
Makes these deeper
Once you know Conditional statements, come back to these — they'll mean more.
- ConditionalsDepth 2An `if` in code is logic's "if P then Q". Knowing the logic is what lets you negate and combine conditions without bugs.
- PredictionDepth 2A prediction has the shape "if this is true, then that will happen".
- ValidityDepth 2The classic valid and invalid forms are built from "if... then" statements - learn conditionals, then come back.