Expression string dump bug?

stephensmitchell · May 7

Simple examples:

clem0338 · May 7

I confirm I can reproduce but only when using VB language

rorourke · May 7

For Expression, this is the behavior I'd expect. C# Expression behaves the same. The statement "5".Dump() outputs to the Results pane because that's the nature of Dump(). Dump() returns the "5" which is the actual expression that also outputs to the Results pane (because that's the nature of the Expression language variants).

JoeAlbahari · May 8

That's right - Dump() is a fluent method that returns the input.

This lets you to inject Dump() into the middle of statements:

new[] { 11, 5, 17, 7, 13 }  .Dump ("Prime numbers")
   .Where (n => n > 10)     .Dump ("Prime numbers > 10")
   .OrderBy (n => n)        .Dump ("Prime numbers > 10 sorted")
   .Select (n => n * 10)    .Dump ("Prime numbers > 10 sorted, times 10!");

and allows this:

DateTime now = DateTime.Now.Dump();

stephensmitchell · May 16

I have a more complex situation where only in vb expressions I'm getting weird duplication issues in the output. It was hard to pin down because my libraries use dump and the particular case is not always a path taken. The solution is to not use dump in those areas. It's important in my use-case because the output is feed into another process. I haven't experienced this in C# for some reason, I believe I should've a least once, but never. I wondered if this was a Visual Basic problem. I understand the behavior is the same for dump.

Expression string dump bug?

Comments

Categories