This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: Name collisions in pythoncore, preventing unity/jumbo build
Type: compile error Stage:
Components: Interpreter Core Versions: Python 3.9
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: Alexander Riccio
Priority: normal Keywords:

Created on 2020-04-02 22:14 by Alexander Riccio, last changed 2022-04-11 14:59 by admin.

Messages (1)
msg365636 - (view) Author: Alexander Riccio (Alexander Riccio) * Date: 2020-04-02 22:14
This isn't a priority issue I'd say. However, fixing it could yield nice benefits. I ran into this while experimenting with JUMBO/Unity builds as part of a bit of fun I've been having tweaking build options across the CPython ecosystem.

Theoretically, a JUMBO/Unity build could reduce code size, improve performance, and maybe even help code analysis detect more bugs by building everything in a single compilation unit. Link Time Code Generation is great, but usually isn't as good as building everything in a single compilation unit.

An example of an interesting thing noticed while compiling as a Unity build:

This exact variable is defined twice in two separate source files, itertoolsmodule.c:4303, and and collectionsmodule.c:1774:

PyDoc_STRVAR(length_hint_doc, "Private method returning an estimate of len(list(it)).");

...the default Release configuration includes this exact string 12 (!) times.

There's a lot of stuff like that. It's not actually broken, and sometimes it's probably inconvenient to fix it (what are you gonna do? put it in a header?), but it would be nice.
Date User Action Args
2022-04-11 14:59:29adminsetgithub: 84342
2020-04-02 22:14:07Alexander Ricciocreate