ghost91-
commented
6 years ago I have already noticed this, too. It is the reason I started looking into other xml libraries. Currently I have implementations for both std-experimental-xml (https://github.com/fsimphy/bayernfahrplan/tree/technical_switch-to-std-expermiental-xml) and dxml (https://github.com/fsimphy/bayernfahrplan/tree/dxml).
Both do currently not work with ldc: dxml needs at least the dmd 2.078.0 front end so it will be possible to use it with ldc once ldc-1.8.0 (which is based on 2.078.3) is released (it is currently in beta). For std-experimental-xml I have no clue what the problem even is, but it looks like a call stack overflow to me (see the failing travis build).
This and the fact that there has been no real development in std-experimental-xml in recent times leads me to the conclusion that at least for now using std-experimental-xml is out of the question. This leaves us with dxml, whicch is a much more promising candidate. My suggestion is to switch to dxml once ldc-1.8.0 is released, I will try to keep the dxml branch up to date until then.
Summary
(up to 60 words)
Steps to reproduce
Actual behaviour
Compilation fails. A full logdump can be found on this gist
Expected behaviour
Software builds and runs.
Context
As Travis builds the project without problems on v2.077.1, this seems to be related with a change in dmd v2.078.0 or later.
This bug emphasizes that we should switch to another xml parser ASAP.
Configuration and environment
Other things to be mentioned
This seems to be an upstream problem, acutally.