slightly tweak description of b_list in comments - #28925
Conversation
I noticed a small typo in the comment describing the use of b_list in
struct basicblock_ ("... that the block are allocated"). Reviewing the
other comments describing use of b_list I then noticed a slight
inconsistency in the description of what it actually points to ("next,"
"early") which I also decided to address here.
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA). Recognized GitHub usernameWe couldn't find a bugs.python.org (b.p.o) account corresponding to the following GitHub usernames: This might be simply due to a missing "GitHub Name" entry in one's b.p.o account settings. This is necessary for legal reasons before we can look at this contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
|
This PR is stale because it has been open for 30 days with no activity. |
|
I signed the CLA, is there anything else I need to do to get this merged? |
# Conflicts: # Python/compile.c
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the |
b_list points to the previously allocated block, not to the next one.
I noticed a small typo in the comment describing the use of b_list in
struct basicblock_ ("... that the block are allocated"). Reviewing the
other comments describing use of b_list I then noticed a slight
inconsistency in the description of what it actually points to ("next,"
"early") which I also decided to address here.