ServiceClosureArgument with private service references original non-existent service

There are of course non-optimal workarounds:

Remove the container.service_locator tag from the service locator [service]. Such that \Symfony\Component\DependencyInjection\Compiler\ServiceLocatorTagPass does not trigger converting args to \Symfony\Component\DependencyInjection\Argument\ServiceClosureArgument

Or,

Do not make the referenced services private.

The solution for this is out of my area. Drupal's Dumpers (\Drupal\Component\DependencyInjection\Dumper\OptimizedPhpArrayDumper, etc, and \Drupal\Component\DependencyInjection\Container are a mystery to me.

Perhaps: build private services and reference them internally via IDs??

The MR I posted fixes my particular issue, but I'm not really happy with it. Similarly the coverage is an adaptation of the coverage added by ✨ Support ServiceClosureArgument in \Drupal\Component\DependencyInjection\Dumper\OptimizedPhpArrayDumper::dumpValue Fixed . However tests still pass after removing implementations.

Changing to Needs Review to solicit feedback about the approach.

So my current workaround is a compiler pass that un-privatises services https://git.drupalcode.org/project/symfony_messenger_scheduler/-/blob/1....

If I remove this workaround, things break.

If I apply the code from the attached MR, and without the workaround, things work again.

Would be great if someone with deeper knowledge of these systems to pick it up. Thanks!

If we can figure out how Symfony does this, we should follow the same path and/or borrow code from them.

Can't figure how it works on a first look, so probably better to start with test

Just moving to NW for test in #9, least that's how I read it.