From c845ce2d89562b13fb10a3bd16c04b7ea39e70c8 Mon Sep 17 00:00:00 2001
From: Christian Flothmann <christian.flothmann@xabbuh.de>
Date: Tue, 15 Apr 2014 18:39:28 +0200
Subject: [PATCH] [Components][DependencyInjection] add note about a use case
 that requires to compile the container

---
 components/dependency_injection/compilation.rst | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/components/dependency_injection/compilation.rst b/components/dependency_injection/compilation.rst
index a90110e4e65..f83a9e8e84d 100644
--- a/components/dependency_injection/compilation.rst
+++ b/components/dependency_injection/compilation.rst
@@ -7,7 +7,9 @@ Compiling the Container
 The service container can be compiled for various reasons. These reasons
 include checking for any potential issues such as circular references and
 making the container more efficient by resolving parameters and removing
-unused services.
+unused services. Also, certain features - like using
+:doc:`parent services </components/dependency_injection/parentservices>` -
+require the container to be compiled.
 
 It is compiled by running::