I understand the motivation to create an object oriented approach for WordPress including Twig.
However, having an autoloader in a plugin or theme seems to be a bad idea, since there is only a global use statement which can not specify which autoloader to use for a specific namespace. So if any other plugin also uses Twig, it can happen that either the other plugin will load the wrong version of Twig or Clarkson-Core will get an outdated version provided by the other plugin.
How is this possible conflict handled?
I understand the motivation to create an object oriented approach for WordPress including Twig.
However, having an autoloader in a plugin or theme seems to be a bad idea, since there is only a global
usestatement which can not specify which autoloader to use for a specific namespace. So if any other plugin also uses Twig, it can happen that either the other plugin will load the wrong version of Twig or Clarkson-Core will get an outdated version provided by the other plugin.How is this possible conflict handled?