--- Comment #27 from klickverbot <> 2012-06-04 03:38:12 PDT 
(In reply to comment #26)
> While the origin and original motivation for pure in D was to enable
> optimizations based on functional purity (multiple calls to the same function
> with the same arguments are guaranteed to have the same results), that's not
> really what pure in D does now, and talking about that clouds the issue
> something awful, as this bug report demonstrates.

I think you've provided a good explanation of the high-level design of the pure
keyword, more than once, but it seems that you are missing that this issue, at
least as stated in comment 3, is actually about a very specific detail: The
extent to which memory reachably by manipulating passed in pointers is still
considered �local�, i.e. accessible by pure functions.

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to