-
Notifications
You must be signed in to change notification settings - Fork 273
Deprecate has_symbol [blocks: #6727] #6766
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
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #6766 +/- ##
===========================================
+ Coverage 77.04% 77.75% +0.71%
===========================================
Files 1594 1568 -26
Lines 185276 179656 -5620
===========================================
- Hits 142748 139698 -3050
+ Misses 42528 39958 -2570
Continue to review full report at Codecov.
|
BTW, there may be a benefit to have a How about designing some sufficiently broad 'symbol expression predicate', which could then be both to both find symbols and do the allocation-free 'has symbol'? (The function, as is, should indeed be deprecated, as there are too many kinds of symbols.) |
The existing code did not permit configuring what kinds of symbols are to be found. It had a single user within the code base, and even that one was not a good use of it for it constructed a single-element set. The new implementation does not yet make use of potential efficiency advantages of "has a symbol" over "find the existing symbols," but such improvements will be done based on further cleanup of find_symbols code.
c32fcb8
to
ea472cb
Compare
As indicated in the (updated) commit message: I intend to address the performance concern in a follow-up commit for it will be a lot easier once the various
Instead of the predicate I'm now using an enum for it may be difficult for a predicate to work as it would need context. |
This improvement is now included in #6727 (commit with subject "Make find_symbols implementations uniform"). |
Closing as #6727 has the full story and the commit of this PR alone is not as meaningful. |
This code does not permit configuration what kinds of symbols are to be
found. It had a single user within the code base, and even that one was
not a good use of it for it constructed a single-element set.