fix issue 16966 - rdmd: AssertError@rdmd.d(489): should have been cre… #204
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…ated by compileRootAndGetDeps
The bug:
On the first run everything is fine.
On the second run,
compileRootAndGetDeps
looks at rdmd.deps to decide if it needs to compile the root module. rdmd.deps is present from the first build, so it looks like everything is up to date and there's apparently no reason to rebuild the root module. But the specified executable doesn't exist, so some code inmain
correctly decides that a rebuild is needed. The build cannot succeed without the root object, of course.This fix:
I'm passing
main
'slastBuildTime
tocompileRootAndGetDeps
and check there if the root module needs to be compiled even when the dependencies don't need to be obtained.That complicates
compileRootAndGetDeps
some more. I'm not really happy with my fix here, but I can't seem to come up with something nicer. rdmd could probably use some refactorings.