Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Extend the information provided by TCling::GetAutoParseClasses

Abierto
  • ¿Algo no está bien?
#23,377 0 comentarios 0 reacciones 2 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@dpiparo ya está trabajando en esto.

Desde el 16/9/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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.

Lenguaje dominante
C++
Estrellas
3.3k
Forks
1.6k
Merge medio
2 d 16 h
PR fusionados (30 d)
194

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de root-project/root

Todos los issues de root-project/root

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.