Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Forbid closing over mutable fields completely

Description

Closing over mutable fields should be forbidden completely (and generate compiler exception), not just when trying to set! them. As the change of the mutable field does not propagate into closed over ones, this leads to surprising bugs:

Environment

None

Activity

Show:

Jozef Wagner December 29, 2014 at 8:21 AM

Thanks for explanation. The ticket is about a proposal that closing over a mutable field should result in error being thrown, an not in a value. If value is desired, an explicit let binding will have to be used. So far, I haven't found a valid use case where closing over mutable field and getting the value closed over is the intended and wanted behavior.

Ghadi Shayban December 29, 2014 at 4:42 AM

In the given example, the close-over happens before the set!, so the closure gets the value, not an assignable container. This is consistent with the rest of the language (pass-by-value not by mutable container)

Jozef Wagner October 10, 2014 at 7:42 PM

related issue

Details

Assignee

Reporter

Priority

Affects versions

Created October 10, 2014 at 7:41 PM
Updated July 19, 2015 at 1:26 PM