@goatcheese @0xabad1dea @pixx
Oh absolutely it can't invent. But
1) rust compile errors prevent some versions of Frankenstein's compiler from even lurching off the table, so Frankenstein has to try again with different body parts (feedback loop)
2) a train of borrowed fragments of rust, that pass that fitness test, and that fit together probabilistically, from a sample of rust code that works (as well as compiles) is more likely to stay on the rails than the same in C.
It is interesting that "correct" but it's a memory hog (no ownership conflicts but lifetime management issues?) is evident from the comparison of gcc vs ccc execution.
I'm not suggesting any sort of magical properties from rust - just that it removes some degrees of freedom.