Skip to content
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

Support for naming code sites #35

Open
npetryk opened this issue Mar 1, 2019 · 0 comments
Open

Support for naming code sites #35

npetryk opened this issue Mar 1, 2019 · 0 comments

Comments

@npetryk
Copy link

npetryk commented Mar 1, 2019

First of all, awesome library that has been incredibly useful! Thanks for all of yall's work

I was thinking that a very useful feature would be to provide names (keywords, most likely) for code sites. Combined with something like last-ep-id this would give you the ability to refer to & debug arbitrary points in your code very easily and without the user having to fiddle with the integer arguments.

My particular motivation is that I have a series of transformations in a big ->> which I scatter with (#(do (def some-name %) %))s. I then shove the captured data into https://github.com/lambdaisland/deep-diff to very clearly see what each transformation step does.

Using spyqt & ep-value for this seems like a no brainer, except for the somewhat tedious cross referencing required to get the call site ids. FWIW this may be useful for #34 in that they could search for the most recent execution id for a specific call site more easily.

Happy to take a crack at it myself in a PR if you'd like to give me your 2 cents about this. Obviously the names would no longer be unique as the integer ids are, and I dont know if this would be an issue for the library.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant