There are a number of rebuilds that can be done as static code analysis. The advantage is, of course, breaking a lot of chicken-egg problems. The class registry is one. The oft-debated hook registry is another. Right now we are building this on-the-fly using the cache layer but this is not quite cache. This of course requires 📌 Use something other than a single underscore for hook namespacing Closed: duplicate . For radical simplifying we could do the theme registry as well -- we are already passing in a single variables array and so hook_theme() is much less necessary. So based on the name of functions and the .tpl.php we can build up the theme registry. It'd be great to have CMI for storing this. We will figure it out what to use instead for now.
When you enable a module then a rebuild.php runs. If you add a new theme function / hook, you run the same.
Postponed: needs info
9.5
Last updated
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Wonder if still a valid task after 11 years?
There has been no work on this task for 13 years. It is likely that it is no longer needed or has been implemented. Therefor, closing.
If there is work to do here, then either re-open the issue and add a comment or open a new issue and reference this one.