Fix Issue 23838 - DMD lexer / parser examples might not compile

[RazvanN7]

This patch:

• updates paths to dub.sdl file
• updates dub.sdl to contain errorsink
• updates the test to compile and run

It seems that the dub tests are not run by the testing pipeline. Anyone knows how to enable them?

If we want dmd as a lib to be usable we should be more careful when breaking the user facing api, such as the constructors of the lexer and parse (cc @WalterBright - you broke the api with your work on the parser/lexer).

Also, one thing to take into account is the fact that the parser expects a null terminated string that is bases as a const(char)[]. So you either use parseModule from frontend.d which adds the \0 or you need to manually add it (as can be seen in the updated test).

[dlang-bot]

Thanks for your pull request and interest in making D better, @RazvanN7! We are looking forward to reviewing it, and you should be hearing from a maintainer soon.
Please verify that your PR follows this checklist:

• My PR is fully covered with tests (you can see the coverage diff by visiting the details link of the codecov check)
• My PR is as minimal as possible (smaller, focused PRs are easier to review than big ones)
• I have provided a detailed rationale explaining my changes
• New or modified functions have Ddoc comments (with Params: and Returns:)

Please see CONTRIBUTING.md for more information.

---

If you have addressed all reviews or aren't sure how to proceed, don't hesitate to ping us with a simple comment.

Bugzilla references

Auto-close	Bugzilla	Severity	Description
✓	23838	normal	DMD lexer / parser examples might not compile

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#15106"

[ghost]

The tests are fixed but are they executed now ?

Anyone knows how to enable them?

If the problem is that they rely on DUB maybe something could be added to the buildkite check then ?

[RazvanN7]

No, they are not enabled now. IIRC they were run at some point, but I have no idea why they were disabled.

Anyway, the retrieveScope test fails with a segfault. I haven't fixed that cause I did not want to bundle too many changes in a single PR. But I will try to find a way to enable these tests in a future pr that also makes the retrieveScope test compile.

[Lyratelle]

frontend is already imported in line 22

[WalterBright]

(cc @WalterBright - you broke the api with your work on the parser/lexer)

I'm not surprised. But I don't know what uses that API outside of the test suite.