If pushNamespace returns a new adapter, what is the use case for popNamespace (which also returns a new adapter, and so won't return the "parent" ArrayAdapter for instance) ?

@stof you're totally right! I removed popNamespace and renamed the pushNamespace method to withSubNamespace.

Ready. Tests should be green after merge.

PR ready (failures will be fixed by merging)

Any comment @symfony/mergers ?

thanks for this great feature @nicolas-grekas

what type-hint that should we use in the constructor to have this ability with autowiring? or NamespacedPoolInterface should be extends CacheInterface ?

Can you try using an intersection type of both? That should work!

i did (https://symfony-devs.slack.com/archives/C3EQ7S3MJ/p1748498675962069?thread_ts=1748446854.832469&cid=C3EQ7S3MJ) but it does not work

[Symfony\Component\DependencyInjection\Exception\RuntimeException]                                                                                                                                                  
  Cannot autowire service "App\Command\TestCommand": argument "$appCache" of method "__construct()" has type "Symfony\Contracts\Cache\CacheInterface&Symfony\Contracts\Cache\NamespacedPoolInterface" but this class  
   was not found.      

Can you open an issue?

issue created #60583