VisualD regressions are severe; what do we do about critical infrastructure?

[ShadoLight]

On Tuesday, 15 October 2024 at 16:25:37 UTC, Manu wrote:
> On Wed, 16 Oct 2024, 01:51 Meta via Digitalmars-d, < 
> digitalmars-d at puremagic.com> wrote:
>
>> On Tuesday, 15 October 2024 at 09:07:12 UTC, Manu wrote:
..
>
> Syntax highlighting takes 10s of seconds, sometimes minutes, 
> and may never
> complete.
> Go-to definition for most symbols don't work.
> Press '.' after an aggregate or an enum or whatever, the list 
> that pops up
> rarely if ever shows any appropriate members or completion 
> suggestions.
> Ctrl-space (complete what I'm typing) doesn't work anymore.
>
> I think it's all related to the new DMD-based semantic analysis 
> bailing out in various situations that I don't understand.
>
> The debugger has significant problems to; important debug 
> features that do essential stuff like show the string for a 
> custom string type have been locking up under unpredictable 
> circumstances.
>

In my experience VisualD often have issues with the latest (or 
even previous version) of VS. I think it was a constant issue for 
Rainer to accommodate the breaking changes from each new version 
of VS. Which version of VS are you using?

Personally I will not even bother to try it with VS 2022.

But I imagine that, since you are targeting micro-controllers, 
you probably don't need the latest and greatest VS - if you can 
tolerate it you can try with VS 2017 (or even 2015) - I still 
have a few issues but most of the stuff you report actually 
worked for me on VS 2015. I've changed some time ago to VS 2017, 
but since then didn't have the time to use VisualD extensively 
... but at least the basics seem to work.