Re: [Chicken-janitors] #1166: Globally defining an identifier previously bound to a macro should shadow the macro fully

[Chicken Trac]

#1166: Globally defining an identifier previously bound to a macro should shadow
the macro fully
---------------------------------+---------------------
            Reporter:  sjamaan   |      Owner:  sjamaan
                Type:  defect    |     Status:  new
            Priority:  major     |  Milestone:  5.1
           Component:  expander  |    Version:
          Resolution:            |   Keywords:
Estimated difficulty:  hard      |
---------------------------------+---------------------

Comment (by sjamaan):

 See also the dreaded #1131; I think this is related to how `##sys#alias-
 global-hook` performs its lookup: it will look up in the environment
 first, and if not found, it will module-rename the symbol if necessary,
 and finally it will just return the symbol as-is, and its bound-at-
 toplevel value will used in that case.  This means any imported bindings
 always take precedence.

 Note that before we enter `##sys#alias-global-hook`, we'll do a lookup in
 `##sys#current-environment` first (in the code walkers in `core.scm` and
 `eval.scm`), so `##sys#alias-global-hook` isn't to blame for this
 particular behaviour.

--
Ticket URL: <https://bugs.call-cc.org/ticket/1166#comment:3>
CHICKEN Scheme <https://www.call-cc.org/>
CHICKEN Scheme is a compiler for the Scheme programming language.