You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Treat object init blocks as a series of separate steps for debugging purposes
Background and Motivation
Given the powerful syntax for collections,etc., sometimes I end up compacting a lot of code into the init block, and currently it's only "one step" - no way to set a breakpoint in the middle, see where exactly an exception is raised from, etc.
Proposed Feature
varx=new Foo
{Prop="abc",List={new Bar
{OtherProp=123,}},};
These new "steps" should be recognized (after x = new Foo):
Set Prop (the Foo instance should be visible in Locals and/or Auto watch windows)
new Bar
Set OtherProp (the Foo and Bar instances should be visible in Locals and/or Auto watch windows)
Add Bar to List (the Foo and Bar instances should be visible in Locals and/or Auto watch windows)
Alternative Designs
N/A
The text was updated successfully, but these errors were encountered:
Summary
Treat object init blocks as a series of separate steps for debugging purposes
Background and Motivation
Given the powerful syntax for collections,etc., sometimes I end up compacting a lot of code into the init block, and currently it's only "one step" - no way to set a breakpoint in the middle, see where exactly an exception is raised from, etc.
Proposed Feature
These new "steps" should be recognized (after
x = new Foo
):Prop
(theFoo
instance should be visible in Locals and/or Auto watch windows)new Bar
OtherProp
(theFoo
andBar
instances should be visible in Locals and/or Auto watch windows)Bar
toList
(theFoo
andBar
instances should be visible in Locals and/or Auto watch windows)Alternative Designs
N/A
The text was updated successfully, but these errors were encountered: