From 1542353af73a795b52e4fa4b5233d149e248c8ed Mon Sep 17 00:00:00 2001 From: Philip Ginsbach Date: Thu, 2 Feb 2023 16:55:06 +0000 Subject: [PATCH] statement no longer holds for namespaces with shadowing --- docs/codeql/ql-language-reference/name-resolution.rst | 3 --- 1 file changed, 3 deletions(-) diff --git a/docs/codeql/ql-language-reference/name-resolution.rst b/docs/codeql/ql-language-reference/name-resolution.rst index 6353c13477e..ebfe4e46e7b 100644 --- a/docs/codeql/ql-language-reference/name-resolution.rst +++ b/docs/codeql/ql-language-reference/name-resolution.rst @@ -266,9 +266,6 @@ Within it, the class ``OneTwoThree`` and the module ``P`` are **visible**, as we Example ======= -The namespaces of a general QL module are a union of the local namespaces, the namespaces of any enclosing modules, -and the global namespaces. (You can think of global namespaces as the enclosing namespaces of a top-level module.) - Let's see what the module, type, and predicate namespaces look like in a concrete example: For example, you could define a library module ``Villagers`` containing some of the classes and predicates that