• H. S. Teoh (7/7) May 18 2019 https://issues.dlang.org/show_bug.cgi?id=19884
• Exil (4/10) May 18 2019 Looks like it was known it would break code? It broke code in
• Petar Kirov [ZombineDev] (22/28) May 18 2019 D's internal infrastructure (druntime, phobos, tools, dub, ...) +
• H. S. Teoh (11/21) May 21 2019 It's actually a standalone project.

"H. S. Teoh" <hsteoh quickfur.ath.cx> writes:

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



This broke one of my projects in a pretty severe way -- deep down in
low-level template mixin code that's very difficult to work around.  :-(


T

-- 
Music critic: "That's an imitation fugue!"

Exil <Exil gmall.com> writes:

On Saturday, 18 May 2019 at 15:18:21 UTC, H. S. Teoh wrote:
 https://issues.dlang.org/show_bug.cgi?id=19884



 This broke one of my projects in a pretty severe way -- deep 
 down in low-level template mixin code that's very difficult to 
 work around.  :-(


 T

Looks like it was known it would break code? It broke code in 
Phobos at least.

Pull Request: https://github.com/dlang/dmd/pull/9769

Petar Kirov [ZombineDev] <petar.p.kirov gmail.com> writes:

On Saturday, 18 May 2019 at 15:18:21 UTC, H. S. Teoh wrote:
 https://issues.dlang.org/show_bug.cgi?id=19884



 This broke one of my projects in a pretty severe way -- deep 
 down in low-level template mixin code that's very difficult to 
 work around.  :-(


 T

D's internal infrastructure (druntime, phobos, tools, dub, ...) + 
the list of projects on BuildKite [0] are the "only" automated 
gatekeepers for breaking changes. Unless a project is added to 
this list, we can't guarantee that there won't be any breaking 
changes, as we have no practical way to ensure that.

The fact that your library broke means that it is particularly 
interesting as apparently it is not covered by this extended test 
suite. If possible, it would be great if you can either:
A) Reduce the part of your code that broke and add it to the dmd 
test suite.
B) Publish the whole or part of your library on GitHub and open a 
pull request to update the BuildKite list [0].

It may sound strange, but this is the only way I can see D 
getting more stable over the years: the more D projects are 
available open-source and the more of them are added to [0], the 
less chance is that a breaking change will go undetected.

P.S. Thanks for testing git HEAD ;)

Cheers,
Petar

[0]: 
https://github.com/dlang/ci/blob/338a692013b9889ceaf2bbc726be94e259ff9708/buildkite.sh#L110

"H. S. Teoh" <hsteoh quickfur.ath.cx> writes:

On Sun, May 19, 2019 at 05:29:40AM +0000, Petar via Digitalmars-d wrote:
 On Saturday, 18 May 2019 at 15:18:21 UTC, H. S. Teoh wrote:
 https://issues.dlang.org/show_bug.cgi?id=19884


[...]
 The fact that your library broke

It's actually a standalone project.


 means that it is particularly interesting as apparently it is not
 covered by this extended test suite. If possible, it would be great if
 you can either:
 A) Reduce the part of your code that broke and add it to the dmd test
 suite.

The reduced code is already in the bug. Presumably that would be added
to the test suite after the bug is fixed.


 B) Publish the whole or part of your library on GitHub and open a pull
 request to update the BuildKite list [0].

[...]

I plan on publishing the code at some point, but right now it's not yet
ready for public consumption.


T

-- 
There are two ways to write error-free programs; only the third one works.