Contextual refinement #20
Open
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
This is the output of my internship. For an extensive overview see my internship report on my website (report | slides)
For a brief summary of changes:
linking.v, essentially gets rid ofMain/Libdisjunction in favor of simply having a registerstate as a second argument to
is_programoris_context.solve_can_linktactic to solve hypotheses that keep appearing in above lemmas.contextual_refinement.vwith a definition of CR and some results about itcontextual_refinement_adequacy.vwhich defines a new relationinterp_exportsrelating exports of componentsand show some results relating this relation to
rtc erased_stepvia adequacy. A large part of this comes from taking the results inexamples/counter_binary_adequacy.vthat don't depend on the counter.examples/counter_binary_adequacy.vto use the above abstractionsmachine_run.vto show equivalence betweenexists n, machine_run _ _ = Some vandexists conf, rtc erased_step _ (v, conf)Let me know if you think this is worth merging into
main. Especially @ageorg29 since I changed your code quite a bit.