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
# just dumping seems to give ok output, in particular for big data-sets:
dump(IOContext(io, :limit=>true), p, maxdepth=1)
end
end)
This seems dangerous, bypassing the whole show machinery. Not to mention, limit should already be set by default in the REPL if I'm not mistaken. This seems more appropriate, giving the same behavior but with the documented interface:
function Base.show(io::IO, ::MIME"text/plain", p::$tn)
ifget(io, :compact, false) ||get(io, :typeinfo, nothing)==$tn
show(IOContext(io, :limit=>true), p)
else# just dumping seems to give ok output, in particular for big data-sets:dump(IOContext(io, :limit=>true), p, maxdepth=1)
endend
I'm not sure always passing :limit => true is a good idea, since that may have been set explicitly to false in the passed in IO.
The text was updated successfully, but these errors were encountered:
So @kwdef changes the show behaviour, right?
For me, the different @show is kinda disturbing my workflow since I can't simply copy paste the printed object into the REPL such that it is valid Julia code again.
Parameters.jl/src/Parameters.jl
Lines 581 to 588 in e55b025
This seems dangerous, bypassing the whole
show
machinery. Not to mention,limit
should already be set by default in the REPL if I'm not mistaken. This seems more appropriate, giving the same behavior but with the documented interface:I'm not sure always passing
:limit => true
is a good idea, since that may have been set explicitly tofalse
in the passed inIO
.The text was updated successfully, but these errors were encountered: