Revert "Merge pull request #5470

[PetarKirov]

This reverts commit 87bdeae, reversing changes made to b5e6365, since it breaks the Dustmite, among probably other projects.

[dlang-bot]

Thanks for your pull request, @ZombineDev!

Bugzilla references

Your PR doesn't reference any Bugzilla issue.

If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog.

[andralex]

So what happened here? I see two unrelated pull requests mentioned.

[PetarKirov]

@andralex The first part of my pull request description was generated automatically by git. It means that your pull-request (#5470) will be reverted and after that the master branch will be in the same state as before (#5470) was merged - the last commit effective commit will be b5e6365 (which remains intact).

(Never mind my previous PR - #5814 - only this one is needed. The difference is that in my previous attempt I used GitHub's revert feature, which for some reason didn't play nice with our Jenkins CI. Now that I used git revert -m 1 87bdeaee41f7bedbc3a5f974eedc013377ef3822 from my local machine and pushed the changes to a branch in my fork as one is supposed to do, it looks like everything is ok.)

[andralex]

I suggest #5816 instead. I plan to expose the functionality publicly but would like to work the kinks out for a release cycle.

[PetarKirov]

Yes, I would prefer #5816 too.