-
Notifications
You must be signed in to change notification settings - Fork 934
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
Listing all available targets? #722
Comments
If this is just for debugging purposes, Otherwise, this would be storing strings indefinitely, which might leak given the current implementation. #678 has more information about that, and #425 currently discusses I'll consider this but right now it's not something I want to support until v5. |
Thanks Qix, I will see if I can help on the memory leak, as a first step before discussing this one :-) I hope your house move was fine, your new job is great and your family bring you hapiness ! Have a nice day |
Sorry for the delayed response - thank you for the kind words @jehon ^^ |
Hello
I would like to list all targets that are available for debug.
I would suggest a list of the strings used:
I have read the comments of the #255, that is suggesting that it would be a memory leak. Is that so? If we cache the "keys" and not the objects, I don't think that it would be a memory leak?
I could submit a PR if this idea is accepted.
The text was updated successfully, but these errors were encountered: