[Chicken-janitors] Re: #398: Nested let-syntax failure to strip renamed identifiers

[Chicken Trac]

#398: Nested let-syntax failure to strip renamed identifiers
-----------------------+----------------------------------------------------
  Reporter:  sjamaan   |       Owner:  felix                        
      Type:  defect    |      Status:  assigned                     
  Priority:  major     |   Milestone:  4.7.0                        
 Component:  expander  |     Version:  4.6.x                        
Resolution:            |    Keywords:  expander, renamed identifiers
-----------------------+----------------------------------------------------
Changes (by felix):

  * owner:  => felix
  * status:  new => assigned


Comment:

 Replying to [comment:11 sjamaan]:
 > Why not add this property setting code to gensym?  It seems like a
 useful thing to keep around on all generated symbols, even outside the
 context of Chicken core.

 I don't know. Gensym is used very often, and I'm not sure such a feature
 would be required very often (the idea has a certain logic to it, yet I
 can't think of much use that would justify the extra code and memory
 requirements).

 >
 > Here's a silly idea: I don't know how and where gensym is usually used,
 but I can imagine it might even make sense to have a procedure (original-
 symbol-name <sym>) which retrieves this property, if available, to "undo"
 gensym calls. If not available, it would just return its argument
 unmodified.

 Hm.

-- 
Ticket URL: <http://gomarketcity.com/ticket/398#comment:12>
Chicken Scheme <http://www.call-with-current-continuation.org/>
Chicken Scheme is a compiler for the Scheme programming language.