search for: d41416

...y  be able to address the issue. The major risk of the task is avoiding code in the clang mainline which is untested by its HEP production environment. There are several other types of patches to the ROOT fork of Clang, including ones  in the context of performance,towards  C++ modules support (D41416), and storage (does not have a patch yet but has an open projects entry and somebody working on it). These patches can be considered in parallel independently on the rest. Extend and Generalize the Language Interoperability Layer Around Cling --- HEP has extensive experience with on-demand pyth...

...able to address the issue. The major risk of the task is avoiding code in the clang mainline which is untested by its HEP production environment. >> There are several other types of patches to the ROOT fork of Clang, including ones in the context of performance,towards C++ modules support (D41416), and storage (does not have a patch yet but has an open projects entry and somebody working on it). These patches can be considered in parallel independently on the rest. >> >> Extend and Generalize the Language Interoperability Layer Around Cling >> --- >> >> HEP h...

...ding code in the clang mainline which is >>>> untested by its HEP production environment. >>>> There are several other types of patches to the ROOT fork of Clang, >>>> including ones  in the context of performance,towards  C++ modules >>>> support (D41416), and storage (does not have a patch yet but has an >>>> open projects entry and somebody working on it). These patches can >>>> be considered in parallel independently on the rest. >>>> >>>> Extend and Generalize the Language Interoperability Layer...

...e to address the issue. The major risk of the task is avoiding code in the clang mainline which is untested by its HEP production environment. >>> There are several other types of patches to the ROOT fork of Clang, including ones in the context of performance,towards C++ modules support (D41416), and storage (does not have a patch yet but has an open projects entry and somebody working on it). These patches can be considered in parallel independently on the rest. >>> >>> Extend and Generalize the Language Interoperability Layer Around Cling >>> --- >>>...

...The major risk of the task is avoiding code in the > clang mainline which is untested by its HEP production environment. > There are several other types of patches to the ROOT fork of Clang, > including ones  in the context of performance,towards  C++ modules > support (D41416), and storage (does not have a patch yet but has > an open > projects entry and somebody working on it). These patches can be > considered in parallel independently on the rest. > > Extend and Generalize the Language Interoperability Layer Around Cling > --- &g...