VisualD regressions are severe; what do we do about critical infrastructure?
GrimMaple
grimmaple95 at gmail.com
Fri Oct 18 17:45:00 UTC 2024
On Tuesday, 15 October 2024 at 09:07:12 UTC, Manu wrote:
> ...
Last time I checked, most of Visual D issues were caused by the
new Visual Studio versions, and it worked somewhat fine on Visual
Studio 2017 (or 2019, you can try that too). As far as it goes, I
would deeply recommend using VS Code instead, as it generally
gives a better experience (visuald sucks, and I only used it a
few times for the debugger)
Also, I encourage you to check out OpenD if you want to see D
moving... _somewhere_, I guess
More information about the Digitalmars-d
mailing list