Rename scoping -> scopeanalyzer, more descriptive.

Technologicat · Technologicat · commit 5b3a3cc4a25f · 2020-09-05T20:06:13.000+03:00
diff --git a/HACKING.md b/HACKING.md
@@ -92,7 +92,7 @@ To study a particular feature, just start from the entry point, and follow the d
 
 The `lazify` and `continuations` macros are the most complex parts. As for the lazifier, grep also for `passthrough_lazy_args` and `maybe_force_args`. As for continuations, read the `tco` macro first, and keep in mind how that works when reading `continuations`.
 
-`unpythonic.syntax.scoping` is a unfortunate artifact that is needed to implement macros that interact with Python's scoping rules, notably `let`.
+`unpythonic.syntax.scopeanalyzer` is a unfortunate artifact that is needed to implement macros that interact with Python's scoping rules, notably `let`.
 
 As of the second half of 2020, the main target platform is Python 3.6, both **CPython** and **PyPy3**. The code should run on 3.4 or any later Python. We have [a GitHub workflow](https://github.com/Technologicat/unpythonic/actions?query=workflow%3A%22Python+package%22) that runs the test suite 
 
diff --git a/doc/macros.md b/doc/macros.md
@@ -840,7 +840,7 @@ because now at the time when ``b`` is forced, the name ``a`` still points to the
 
 If you're sure you have *new definitions* and not *imperative updates*, just manually use ``lazy[]`` (or ``lazyrec[]``, as appropriate) on the RHS. Or if it's fine to use eager evaluation, just omit the ``lazy[]``, thus allowing Python to evaluate the RHS immediately.
 
-Beside function calls (which bind the parameters of the callee to the argument values of the call) and assignments, there are many other binding constructs in Python. For a full list, see [here](http://excess.org/article/2014/04/bar-foo/), or locally [here](../unpythonic/syntax/scoping.py), in function ``get_names_in_store_context``. Particularly noteworthy in the context of lazification are the ``for`` loop and the ``with`` context manager.
+Beside function calls (which bind the parameters of the callee to the argument values of the call) and assignments, there are many other binding constructs in Python. For a full list, see [here](http://excess.org/article/2014/04/bar-foo/), or locally [here](../unpythonic/syntax/scopeanalyzer.py), in function ``get_names_in_store_context``. Particularly noteworthy in the context of lazification are the ``for`` loop and the ``with`` context manager.
 
 In Python's ``for``, the loop counter is an imperatively updated single name. In many use cases a rapid update is desirable for performance reasons, and in any case, the whole point of the loop is (almost always) to read the counter (and do something with the value) at least once per iteration. So it is much simpler, faster, and equally correct not to lazify there.
 
diff --git a/unpythonic/syntax/lazify.py b/unpythonic/syntax/lazify.py
@@ -193,7 +193,7 @@ def is_literal_container(tree, maps_only=False):
 #   - keep in mind that force(x) == x if x is a non-promise atom, so a wrapper is not needed
 #   - don't lazify "with", eager init is the whole point of a context manager
 #   - don't lazify "for", the loop counter changes value imperatively (and usually rather rapidly)
-# full list: see unpythonic.syntax.scoping.get_names_in_store_context (and the link therein)
+# full list: see unpythonic.syntax.scopeanalyzer.get_names_in_store_context (and the link therein)
 
 def lazify(body):
     # first pass, outside-in
diff --git a/unpythonic/syntax/letdo.py b/unpythonic/syntax/letdo.py
@@ -32,7 +32,7 @@
 from ..dynassign import dyn
 from ..misc import namelambda
 
-from .scoping import scoped_walker
+from .scopeanalyzer import scoped_walker
 from .letdoutil import isenvassign, UnexpandedEnvAssignView
 
 def let(bindings, body):
diff --git a/unpythonic/syntax/scopeanalyzer.py b/unpythonic/syntax/scopeanalyzer.py
