-
Notifications
You must be signed in to change notification settings - Fork 256
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.
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
Bug: Using Dafny.dll to build an AST fails if no compiler specified. #1932
Comments
Can you give a repro for this issue? The option-parsing code does |
In other words, it's intended that |
The method |
Initializing a compiler instance doesn't really do that much, so it would be fine to initialize the compiler to be the C# one. But isn't it good that you get an error? It tells you that your code may depend on the internals of the compiler, which is good to know? |
When this does bug occur? It seems like it occurs if |
Yes indeed. However, previously, parsing would succeed even though DafnyOptions.O is not properly initialized. Users setting themselves the options without depending on our custom initialization faced the problem of having a field that is uninitialized (Compiler), which break their code. |
Since #1894 ,
ModuleExportDecl.FullCompileName
used in the constructor ofModuleExportDecl
can throw a null pointer exception becauseTopLevelDecl.FullCompileName
now depends onDafnyOptions.O.Compiler
, which does not have a default value.The text was updated successfully, but these errors were encountered: