.NET Framework 4.6.2

Re:.NET Framework 4.6.2 by ygra on Wednesday August 03, 2016 @03:34AM (#12216298)

But you can already debug inside lambda expressions. E.g. for

     new string[] { "1", null }.Select(s => s.Length).ToList();

VS has no trouble at all telling me the statement that caused the NRE and I can inspect variables local to the lambda as well.

[ Parent | on HN ]

Re:.NET Framework 4.6.2 by pionar on Wednesday August 03, 2016 @11:16AM (#12218541)

But you can't always debug code that's out in the wild with the same exact scenario that caused the NRE.

It's helpful to have the actual thing that's null for post-error troubleshooting.

[ Parent | on HN ]

Re:.NET Framework 4.6.2 by ygra on Wednesday August 03, 2016 @11:45AM (#12218763)

The whole discussion is about a debugger feature, or at least, the runtime groundwork required for said debugger feature. It will not result in the exception message telling you the null reference's name. It enables an attached debugger to query the runtime for additional information to determine that.

[ Parent | on HN ]