Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Extend the information provided by TCling::GetAutoParseClasses

Aperta
  • Qualcosa non va?
#23,377 0 commenti 0 reazioni 2 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@dpiparo ci sta già lavorando.

Dal 16/9/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

in:Core Libraries new feature

TCling::GetAutoParseClasses (and its Print counterpart) only provides the list of class name that directly triggered the auto-parsing of header files.

As seen in https://github.com/cms-sw/cmssw/issues/49458 (see around https://github.com/cms-sw/cmssw/issues/49458#issuecomment-5455974884), sometimes this is not the name of the class for which we are missing a dictionary.

For example we could have a class template sometemplate with 2 arguments and where the 2nd argument is irrelevant to I/O (does not participate in I/O, does not affect the I/O layout of the class template instance).

In such a case, the user would request the dictionary for the first argument and for the template instance.

In the error case (only have the dictionary for class A but inadvertently not for sometemplate<A, B> and intentionally not for B.

In that case the capture of the trigger of the auto-parsing will happen in the stack trace like:

- GetClass("sometemplate<A, B>");
- Successful auto-parse of B which also makes "sometemplate<A, B>" available.

In the CMS' case B is complex enough that the auto-parse can succeed even without a dictionary for the actual B (which is a class instance).

The auto-parse report would in this case only mention B (which is expected to not have a dictionary) where as the user need to know about sometemplate<A, B> in order to fix the proper missing dictionary.

To solve this issue the auto-parse report would need to gather the list of classes being looked up (by a TClass::GetClass) when an auto-parse happens.

One challenge is to minimize the impact of the common case (no error and no reporting needed) - This may or may not require to make the recording optional.

Lingua principale
C++
Stelle
3.3k
Fork
1.6k
Merge medio
2g 16h
PR unite (30g)
194

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di root-project/root

Tutte le issue di root-project/root

Issue simili

Altre issue su C++

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.