Opened 6 years ago

Closed 5 years ago

#158 closed defect (fixed)

mutating imports

Reported by: alexshinn Owned by: alexshinn
Priority: major Milestone:
Component: WG1 - Core Keywords:


Currently the semantics of calling set! or define
on an imported binding is undefined. Do we
want to specifically make this an error?

Change History (5)

comment:1 Changed 6 years ago by cowan

I think we want importing bindings to be immutable in a module and mutable at the REPL.

comment:2 Changed 6 years ago by arcfide

R6RS, Chez's Modules, and Racket's module forms all, to my knowledge enforce immutability constraints on imported identifiers. I am inclined to think that this is something we want to maintain. I think immutable imports makes more sense both from efficiency and code reasoning perspectives. Otherwise, I think we could have a lot of confusion concerning bindings and evaluation orders when invoking libraries.

comment:3 Changed 6 years ago by alexshinn

  • Status changed from new to decided

We voted this is an error.

comment:4 Changed 6 years ago by alexshinn

  • Status changed from decided to writing

comment:5 Changed 5 years ago by cowan

  • Resolution set to fixed
  • Status changed from writing to closed
Note: See TracTickets for help on using tickets.