This fixes ROOT-10057

/build/jenkins/night/LABEL/mac1014/SPEC/cxxmod-noimt/root/test/testGenVectorVc.cxx:194:1: error: redefinition of 'Point' as different kind of symbol
using Point = ROOT::Math::PositionVector3D<ROOT::Math::Cartesian3D<T>, ROOT::Math::DefaultCoordinateSystemTag>;
^
In module 'Darwin' imported from /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/assert.h:42:
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/MacTypes.h:538:8: note: previous definition is here
struct Point {
^

See  http://root-forum.cern.ch/t/tselector-ttreereader-and-fchain-setentry/30170/1
and http://root-forum.cern.ch/t/problem-with-multiple-files-in-tchain-with-makeselector-class/32534/7

Without this patch for Name<Content>::Inner, MakeProject was using Name<Content,::Inner>::Inner.

in order to make of this code the most up-to-date set of examples possible.

GetEntry is not thread-safe anyway, and GetEntriesUnsafe is faster.

GetEntriesFast is not as fast as it could be: it constructs and
destructs a TReadLockGuard, and might need to modify fLast.
GetEntriesUnsafe is a thread-unsafe version of GetEntriesFast
that side-steps these operations when possible.

The operation is relatively costly as TObjArray::GetEntries also
creates a TReadLockGuard.

From V.Vasilev, it fixes:
[ 72%] Building CXX object interpreter/llvm/src/tools/clang/lib/CodeGen/CMakeFiles/clangCodeGen.dir/CodeGenModule.cpp.o
While building module 'Cling_Interpreter' imported from /.../root/core/clingutils/src/RStl.cxx:25:
In file included from <module-includes>:5:
 /.../root/interpreter/cling/include/cling/Interpreter/RuntimeUniverse.h:13:2: error: "This file must not be included by compiled programs."
 #error "This file must not be included by compiled programs."
 ^

...wherever it's more readable, less error-prone than the alternatives.

This is an extension allowing the VMC package to run a simulation
with multiple different engines at a time. Tracks can be transferred
among engines during a simulation run based on conditions specified by
the user.

Important notes on the extensions:
  1) This extension preserves backward-compatibility in the sense that
     user code relying on the former version of VMC is still running
     with the extended version. Was tested with GEANT3_VMC@v2-6 and
     GEANT4_VMC@v3-6-p1.
  2) A shared simulation is only possible when TGeo is used for geometry
     construction and navigation.
  3) A TMCManager singleton object is responsible for handling multiple
     engines and can be obtained on request calling
     TVirtualMCApplication::RequestManager() during construction of the
     user application class.
  4) The introduced TMCParticleStatus objects hold additional
     information to keep track of properties when a track is transferred
     between engines.
  5) When a track is interrupted in one engine to be transferred to
     another, the geometry state is cached in the form of a
     TGeoBranchArray object. It will be used to initialize the navigator
     when this track is picked up for further transport in the next
     engine. This is especially useful/required when a track is
     transferred at a volume boundary in order to be picked up in the
     entered volume and not in the one just left. This is a main reason
     why geometry management is forced to be done via TGeo.

A more comprehensive introduction concerning the usage and
implementation in the user code can be found in the
montecarlo/vmc/README.md

Further note:
  This commit also applies the clang format to the modified and new
  files.

The getNameAsString interface causes a lot of temporary allocations.
The analysis if a decl is a cling-style wrapper can work only on a
simple declarations on the global scope.

This patch filters out complex declarations (eg in namespaces) and
checks only the identifier content.

The patch reduces the memory footprint difference shown in root-project/root#3012.

This allows TMVA to create a pool of threads on demand and fixes ROOT-10034

This reverts commit 3efc1356.

Duplicating Cling_Runtime and Cling_Runtime_Extra in both module.modulemap
and module.modulemap.build causes redefinition errors if -Dbuiltin_clang=Off.
We should not duplicate the cling runtime modules in both modulemaps.

This is a cherry pick of the loader.py in cppyy-backend
version clingwrapper-1.7.2, which has the new treatment of
CLING_STANDARD_PCH and its setting to 'none' to prevent
the PCH check by Cppyy.

A complete update will come for the three packages of Cppyy
once the functionality of this PR:
https://github.com/root-project/root/pull/3579
is merged into TCling.