Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork33.3k
gh-118771: Ensure names defined in optimizer.h start with Py/_Py#118825
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
I'll leave this for@markshannon to review. |
brandtbucher commentedMay 9, 2024 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
I personally don't think we should be exposing this much of the micro-op format. Can they just be moved to |
Yes, let's move as much as we can to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
@encukou Thanks for tidying that up
Uh oh!
There was an error while loading.Please reload this page.
optimizer.his included fromPython.h, and defines some names that can clash with user code. They should be hidden or get thePy/_Pyprefix.This PR:
struct _bloom_filterstruct _exit_data_Py_:uop_get_targetuop_get_exit_indexuop_get_jump_targetuop_get_error_targetoptimize_functypedefBLOOM_FILTER_WORDSUOP_FORMAT_TARGETUOP_FORMAT_EXITUOP_FORMAT_JUMPUOP_FORMAT_UNUSEDPerhaps some of these should be in a private header instead?
Or perhaps some should be public?
@markshannon, could you clarify the intent here?
Py/_Pyprefix #118771