Extraction.Krml: properly detect mem type, it does not have an argument #3455
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.
(ccing @msprotz since we were really surprised this would fail, but perhaps most krml invocations are done including an extracted ulib, wondering if it's worthwhile to add a test for this somewhere --- commit message below)
Previous to this patch, extracting this snippet to kmrl:
Would result in:
Note the binding for
h
at typeFStar.Monotonic.HyperStack.mem
, defined asEUnit
. This comes from the definition ofupd
as wrapper:Now, if we try to actually extract C code, it works fine, but apparently only since karamel knows the definition of the
mem
, since it is in the krml file, and erases it. Tightening the--extract
makes it fail with a type mismatch, and the function is skipped.