As per Luke's instructions I've updated the [wishlist item][1]
to include the deparse-on-error issue, and also renamed it to
something more appropriate for its broader scope.
I do share Lionel's concern that the deparse-on-error issue
could get unnecessarily delayed in the hopes of finding a more
We also have a few other suggestions and wishes about backtrace
storage and display on the one hand, and display of constructed calls
on the other hand. Perhaps it would be better to open a different
wishlist item for traceback() to keep the discussions focused?
FWIW I think deparsing backtraces l
Better to add this to the wishlist item. This all needs to be looked
at together, and nothing is likely to happen until after
vacation/conference season. It will disappear from everyone's radar
if it is just in R_devel.
Best,
luke
On Sun, 14 Jul 2019, brodie gaslam wrote:
> Luke, thanks for co
Luke, thanks for considering the issue. I would like to
try to separate the problem into two parts, as I _think_
your comments address primarily part 2 below:
1. How can we avoid significant and possibly crippling
stalls on error with these non-standard calls.
2. What is the best way to view
This is probably best viewed in the context of other issue with
displaying calls, such as issues arising from calls constructed in
non-standard evaluation contexts. Might be good to move to a wishlist
item in bugzilla.
Best,
luke
On Sat, 13 Jul 2019, brodie gaslam via R-devel wrote:
> When larg
