Avoid creation of a temporary probe file for newer compilers #1316
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.
When I chated with @RazvanN7 today, he complained about DUB creating a lot of temporary probing files in his current working directory.
A quick look at the code revealed that DUB uses this probing hack to extract information
from DMD. Since dlang/dmd#6880 (2.076.0), it's possible
to avoid the need of creating a temporary file for this hack.
Of course, it would be better to read this file from the compiler directly...