When setting a breakpoint on an anonymous function, the IL Debugger sets two breakpoints, one in the definition of the anonymous function and one inside the function when it gets executed.
I think it would be more correct if the breakpoint got only hit, when the code inside the function is executed and not when the function is defined
To change this behaviour is not very difficult: in the function SetBreakpoint from the Debugger.Core only the narrowest SequencePoint should be used to set the breakpoint.
Before I make the effort to create a pull request for this issue, I would want to know if this is the intended behaviour or if it is desirable to change it like I described.
Anyone can give some feedback on this?