fix Issue 19140 - AssertError@dmd/ctfeexpr.d(229): Assertion failure

[ibuclaw]

https://issues.dlang.org/show_bug.cgi?id=19140

When compiling with -verrors=spec

(spec:1) test/compilable/interpret3.d(7751): Error: f19140 cannot be interpreted at compile time, because it has no available source code
(spec:1) Error: cannot implicitly convert expression <error> of type void to real

[dlang-bot]

Thanks for your pull request, @ibuclaw!

Bugzilla references

Auto-close	Bugzilla	Severity	Description
✓	19140	regression	[REG master] AssertError@dmd/ctfeexpr.d(229): Assertion failure

⚠️⚠️⚠️ Warnings ⚠️⚠️⚠️

• Regression or critical bug fixes should always target the stable branch. Learn more about rebasing to stable or the D release process.

To target stable perform these two steps:

1. Rebase your branch to upstream/stable:

git rebase --onto upstream/stable upstream/master

2. Change the base branch of your PR to stable

Testing this PR locally

If you don't have a local development environment setup, you can use Digger to test this PR:

dub fetch digger
dub run digger -- build "master + dmd#8537"

[RazvanN7]

Please re-target stable.

[ibuclaw]

No, because this is a regression only in master.

[ibuclaw]

Also, I'll be rebasing gdc against master on a weekly basis, so all these implementation regressions will be rooted out long before release. ;-)

[wilzbach]

@CyberShadow any idea why DAutoTest is now permanently failing?
The logs only show this:

dmd/dinifile.d(99): Error: file `"SYSCONFDIR.imp"` cannot be found or not in a path specified with `-J`

...

posix.mak:469: recipe for target '../generated/linux/release/64/dmd' failed
make: *** [../generated/linux/release/64/dmd] Error 1

[CyberShadow]

@CyberShadow any idea why DAutoTest is now permanently failing?

It doesn't look like a permanent failure judging from the branch history:
http://dtest.dlang.io/history/master

Perhaps bad dependencies in the makefile causing an unstable build order?