minor #9157 do never fetch private services from the container (xabbuh)

javiereguiluz · javiereguiluz · commit e2c4a432d4e3 · 2018-01-29T09:17:52.000+01:00
This PR was merged into the 2.7 branch. Discussion ---------- do never fetch private services from the container Explaining that private services can still be fetched from the container under certain circumstances does not look like a good idea. Not only is it hard to grasp for beginners to understand why this sometimes works. It also becomes a real problem when upgrading to Symfony 4 where all private services won't be retrievable from the container through service location. Commits ------- fedc522 do never fetch private services from the container
diff --git a/service_container/alias_private.rst b/service_container/alias_private.rst
@@ -57,12 +57,11 @@ What makes private services special is that, if they are only injected once,
 they are converted from services to inlined instantiations (e.g. ``new PrivateThing()``).
 This increases the container's performance.
 
-Now that the service is private, you *should not* fetch the service directly
+Now that the service is private, you *must not* fetch the service directly
 from the container::
 
     $container->get('foo');
 
-This *may or may not work*, depending on if the service could be inlined.
 Simply said: A service can be marked as private if you do not want to access
 it directly from your code.
 
