fix Issue 14639 - Assigning init value to struct uses stack, causing …

[WalterBright]

…segfault

[dlang-bot]

Thanks for your pull request, @WalterBright!

Bugzilla references

Auto-close	Bugzilla	Severity	Description
✓	14639	normal	Assigning init value to struct uses stack, causing segfault

Testing this PR locally

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

dub run digger -- build "master + dmd#6766"

[UplinkCoder]

@WalterBright fails in runnable/sdtor.d

[andralex]

I'm unclear about this. The test seems to imply that .init is an rvalue for all types. Is that the case?

[PetarKirov]

You can't get the address of .init so yes, it behaves like an rvalue, even though it's stored in the binary, AFAIK.

[Geod24]

You can safely ignore the C++ interop tests

[WalterBright]

Howz about an approval, then? :-)

[Geod24]

Does it still work to disable opAssign ? Do we have a test for that ?

[WalterBright]

The hasBlitAssign only is set for generated opAssign, which won't happen for disabled opAssign.

[WalterBright]

Thank you. It'll be good to put this old issue to rest.