Null interception in PrettyPrinter #88
kindermannhubert
started this conversation in
General
Replies: 2 comments
|
@kindermannhubert the reasoning is to avoid the following behavior, where assignments (e.g. I agree that the behavior in csi.exe is better here, where it doesn't display null for assignments, but does display in cases where the object being evaluated is null -- I believe back when this was written (a while ago now!) I didn't see a way of distinguishing the two cases in the script evaluation API. |
0 replies
|
Indeed Roslyn provides no information on whether the input is void-returning/no-output or value-returning. I've prepared a custom analysis of this in #187. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment


Uh oh!
There was an error while loading. Please reload this page.
@waf what is the reasoning behind this?

csi.exe and Immediate window in VS also outputs
nulltext and I would probably prefer it too.This could surely be configurable but I'm not sure if it's necessary.
All reactions