How can we make it easier to experiment with the compiler?

[Alexandru Ermicioi]

On Sunday, 23 May 2021 at 06:12:30 UTC, Ola Fosheim Grøstad wrote:
>
> 7. Tutorials.

8. Proper module naming, not abbreviations. Abbreviations need to 
be remembered, and that is additional mental workload for new 
volunteer.
9. Proper variable naming, not abbreviations. I really tried to 
understand some code, but got discouraged once met all those 
abbreviated variable names, I literally had to stuff all my 
memory with what those abbreviations meant instead of trying to 
keep the thread of the logic that code is implementing.
10. Split up humongous methods and objects, they are rude to new 
volunteers, and discourages any code improvement.
11. Perhaps some tutorial, on how to orient in all dmd internals, 
with a nice abstract class diagram explaining key elements of dmd 
objects and how they interact between themselves. This would 
allow at least some kind of overview of what does what in dmd, 
and how they interact.

I really was interested in doing some dmd bug fixes, but 8,9, and 
10, make the code to take too much time, and willpower to just 
understand it. It was and is a huge barrier for me to try and 
fix/improve dmd.

P.S. And no, e,exp,aa and other kind of abbreviations except for 
loop indexes, are not always obvious, and do take mental power 
and memory, while trying to understand existing code. They are 
not simple for new volunteers to dmd.

Best regards,
Alexandru.