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
Currently, Dafny allows an opaque type to be listed both in the provides list and the reveals list of an export set. There's no difference between these two. Therefore, to be consistent with other restrictions, it seems logical to forbid an opaque type from being listed in a reveals clause. (Ror example, compare with a method declaration, which is not allowed in a reveals clause.)
Example:
module M {
export A
provides OpaqueType
export B
reveals OpaqueType // this ought not to be allowedtype OpaqueType
}
The text was updated successfully, but these errors were encountered:
Currently, Dafny allows an opaque type to be listed both in the
provides
list and thereveals
list of an export set. There's no difference between these two. Therefore, to be consistent with other restrictions, it seems logical to forbid an opaque type from being listed in areveals
clause. (Ror example, compare with amethod
declaration, which is not allowed in areveals
clause.)Example:
The text was updated successfully, but these errors were encountered: