-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tidy up dump and xdump #4163
Comments
Solution could be as simple as deleting |
But would the |
There should only be one and it should give you all of the information in a somewhat readable form. Currently sometimes |
Ok, thanks! I've been using dump and xdump a lot lately, so I'll try to come up with something to everybody's satisfaction. |
Buggy with function arguments (similar on jb/functions):
|
on master julia> dump(x->x)
#1
julia> dump(x->x)
#3
julia> dump(x->x)
#5 Is this supposed to say |
fix #4163, remove `xdump` and simplify `dump`
These functions have become a basket of odd behaviors, and their implementation is quite complex.
There are differences like this:
Then there is this:
The first output was fine, but put it inside a tuple and something else happens.
Also
xdump
is not documented. If the current behavior does actually make sense, then the task here is to explain it by documentingdump
andxdump
better.But I propose that we should only have
dump
, and it should simply traverse a structure and show everything about it.The text was updated successfully, but these errors were encountered: