Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Separate compilation issues #980

Open
Tracked by #501
davidcok opened this issue Dec 17, 2020 · 2 comments
Open
Tracked by #501

Separate compilation issues #980

davidcok opened this issue Dec 17, 2020 · 2 comments
Assignees
@keyboardDrummer
Labels
priority: not yet Will reconsider working on this when we're looking for work status: needs-info Issue requires more information from poster

Comments

@davidcok
Copy link
Collaborator

davidcok commented Dec 17, 2020 •
edited
Loading

The ability to declare a nested module outside its "enclosing" module makes separate compilation of files and modules more challenging. By some mechanism a separately compiled portion of a program needs a hash of all the parts it depends on, which hash can be checked at link time to be sure that the depended on parts did not change between the time dependers are compiled and the depended on parts are compiled.

An additional problem -- even if there is no circularity among modules, there may still be among files.
@RustanLeino RustanLeino added this to the Post 3.1 milestone Jan 13, 2021
@robin-aws
Copy link
Member

Related to #501

@robin-aws robin-aws mentioned this issue Jan 13, 2021
Open
8 tasks
@keyboardDrummer
Copy link
Member

keyboardDrummer commented Jul 19, 2021 •
edited
Loading

@davidcok What's the desired outcome of this issue?

My understanding is that Dafny currently doesn't have incremental compilation. If the desired outcome is to have that, shouldn't that be the issue title?

@keyboardDrummer keyboardDrummer self-assigned this Jul 19, 2021
@keyboardDrummer keyboardDrummer added the status: needs-info Issue requires more information from poster label Jul 19, 2021
@robin-aws robin-aws removed this from the Post 3.1 milestone Sep 22, 2021
@MikaelMayer MikaelMayer added the priority: not yet Will reconsider working on this when we're looking for work label Aug 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@keyboardDrummer keyboardDrummer

Labels
priority: not yet Will reconsider working on this when we're looking for work status: needs-info Issue requires more information from poster
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@keyboardDrummer @MikaelMayer @davidcok @RustanLeino @robin-aws