Visual D Debugger "complaints" (Mago?)

[StarGrazer via Digitalmars-d-ide]

On Sunday, 19 June 2016 at 08:06:55 UTC, Rainer Schuetze wrote:
>
> On 18.06.2016 17:57, Joerg Joergonson wrote:
>> [...]
>
> Visualizers in a separate module or even binary have the 
> problem of not being able to access private symbols. Having it 
> in a DLL built and loaded by mago/vd needs an extensive API for 
> reflection and memory access. This seems like a larger 
> project...
>
> I'd rather start with some functions in the debuggee itself to 
> be searched for the type data to be displayed, e.g.
>
> string mago_visualizer(ref T data);
> string mago_visualizer(T)(ref T data);
>
> or some sink-delegate-version to avoid allocations.
>
> mago will try to resolve these for T and its base classes. If 
> it finds one, it is called and the string result is displayed.

Has anything like this been added yet?  I would like to be able 
to see the GUID value in the debugger, but it is not showing up...