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
#5651)
Fixes#5650
### Description
Verification in the IDE now works correctly when declaring nested module
in a different file than their parent.
### How has this been tested?
Added an IDE test
<small>By submitting this pull request, I confirm that my contribution
is made under the terms of the [MIT
license](https://github.com/dafny-lang/dafny/blob/master/LICENSE.txt).</small>
That workaround doesn't work so well when you have lots of nested modules (e.g., when they represent various implementations of an interface).
The workaround I've been using for module foo is to keep foo.dfy in the same folder, and to also add into the foo directory a dfyconfig.toml file of the form
base = "../dfyconfig.toml"
excludes = ["foo.dfy"]
This hides foo.dfy when building files under foo, while allowing foo.dfy (and all of the other files in the foo hierarchy) to be used by all modules that do not descend from foo.
Dafny version
4.6.0 (nightly 4/17)
Code to produce this issue
With the following files (all in the same directory), the dafny server fails on b.dfy.
(building the dfyconfig file works)
a.dfy: a {}
b.dfy: module a.b { method test() { assert true; }}
dfyconfig.toml: includes = ["*.dfy"]
Command to run and resulting output
No response
What happened?
verification should succeed.
more generally, there should be uniformity between the CLI and the Dafny server.
What type of operating system are you experiencing the problem on?
Mac
The text was updated successfully, but these errors were encountered: