You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This needs more investigation, but the cause might due to the fact that when we instantiate a module we substitute concrete types into the schemas of some things. This might cause certain predicates in the qualified types to become True and thus disappear, but then the underlying term is incorrect because it expects evidence for something which is now gone.
The text was updated successfully, but these errors were encountered:
yav
changed the title
Incorrect IR after module insantiation
[New module system] Incorrect IR after module insantiation
Oct 12, 2022
There's also an issue if we change the above example to instantiate F with 1 in which case the predicate would become False. Apparently coreLint does not like that, so we need to investigate why that is.
To reproduce:
cryptol-specs
:set coreLint=on
:load Primitive/Keyless/Hash/SHA2/SHA512.cry
This needs more investigation, but the cause might due to the fact that when we instantiate a module we substitute concrete types into the schemas of some things. This might cause certain predicates in the qualified types to become
True
and thus disappear, but then the underlying term is incorrect because it expects evidence for something which is now gone.The text was updated successfully, but these errors were encountered: