| ▲ | Frost1x 30 minutes ago | |||||||||||||
That’s the purpose of Lean. It’s kind of like asking: how do you know your CPython is running all the correct binary? Well, you kind of don’t, as it’s beyond human comprehension (in theory you could trace everything down to a certain level) but there are layers and layers of build abstraction that you assume are correct, compilers, runtime environments, and mature libraries that are checked and validated. Not a perfect analogy but that’s kind of the gist of it. | ||||||||||||||
| ▲ | lossolo 23 minutes ago | parent [-] | |||||||||||||
OK, but if I write code, I can verify it in a few simple steps. What about 250k pages of proof? How can I verify that page 133,432 has the correct assumptions and that it isn't reward hacked just to make lean code pass? How it's done? | ||||||||||||||
| ||||||||||||||