This project is read-only.

Breakpoint Diagnostics

Topics: C# Language Design, VB Language Design
Oct 22, 2014 at 10:13 PM
This topic is to further a discussion on another thread, as not to taint that topic
nmgafter wrote:
AdamSpeight2008 wrote:
What about debug breakpoint diagnostics? Where that actual object values are available?
For example class object is null, give a warning.
I don't understand what you're asking. Can you show a concrete scenario?
Currently diagnostics are only applicable at compile-time (as far as I know).
A Debug Breakpoint Diagnostic would be applicable when you hit a breakpoint.

This would enable more powerful diagnostics since you have access also the value. It doesn't restrict it to only compile-constants and literals.

Let's say we have one that greyed out variable usage when that variable contains a class type and it's value is null.

Or one the change the colour of a boolean if it true -> Green, false -> Red
Nov 7, 2014 at 11:53 PM
AdamSpeight2008 wrote:
This topic is to further a discussion on another thread, as not to taint that topic
nmgafter wrote:
AdamSpeight2008 wrote:
What about debug breakpoint diagnostics? Where that actual object values are available?
For example class object is null, give a warning.
I don't understand what you're asking. Can you show a concrete scenario?
Currently diagnostics are only applicable at compile-time (as far as I know).
A Debug Breakpoint Diagnostic would be applicable when you hit a breakpoint.

This would enable more powerful diagnostics since you have access also the value. It doesn't restrict it to only compile-constants and literals.

Let's say we have one that greyed out variable usage when that variable contains a class type and it's value is null.

Or one the change the colour of a boolean if it true -> Green, false -> Red
This is an interesting idea for us to look at as we design the next major version.