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
I'd like to be able to say which locals were arguments to the function, which were bound inside the function, which are captures in closures. For arguments we have both the initial values available - what they were as arguments, as well as what they are now, if they have changed.
The text was updated successfully, but these errors were encountered:
That seems like a great idea. frame-locals-for-emacs in swank.lisp and frame-locals (in each backend) construct a plist for each local. Seems straightforward to add that extra information you suggest.
Then sldb-show-frame-defails can show that information somehow. Maybe it can add a new "Arguments:" section if any of the locals are tagged as being an argument.
I'd like to be able to say which locals were arguments to the function, which were bound inside the function, which are captures in closures. For arguments we have both the initial values available - what they were as arguments, as well as what they are now, if they have changed.
The text was updated successfully, but these errors were encountered: