bpo-36876: Make some static string literal arrays constant.#15760
bpo-36876: Make some static string literal arrays constant.#15760ericsnowcurrently wants to merge 7 commits into
Conversation
pganssle
left a comment
There was a problem hiding this comment.
Looks good overall, a few formatting nits around whitespace I found.
Sorry, something went wrong.
|
When you're done making the requested changes, leave the comment: |
Sorry, something went wrong.
pganssle
left a comment
There was a problem hiding this comment.
Here are all the alignment issues I found. Hopefully the "suggestions" are the right number of spaces.
Sorry, something went wrong.
|
Changing It is possible to change the API, but it is long a complex process. It is a separate issue. Adding consts in |
Sorry, something went wrong.
|
Note also that you can add two See #15824 for changes in |
Sorry, something went wrong.
Co-Authored-By: Paul Ganssle <p.ganssle@gmail.com>
Co-Authored-By: Paul Ganssle <p.ganssle@gmail.com>
Co-Authored-By: Paul Ganssle <p.ganssle@gmail.com>
Co-Authored-By: Paul Ganssle <p.ganssle@gmail.com>
Co-Authored-By: Paul Ganssle <p.ganssle@gmail.com>
|
Hmm, this won't work out. |
Sorry, something went wrong.
|
At the time there is a bunch of forgotten const / const_cast / The list includes the following pip packages (but definitely not limited to): Is there any way to continue working on the issue? |
Sorry, something went wrong.
|
@serhiy-storchaka, could you, please, elaborate on
At the time the lack of const causes problems i. e. when compiling in MSVC standard conformance mode (which is default for |
Sorry, something went wrong.
This gives us guarantees about immutability.
https://bugs.python.org/issue36876