On 8/29/2018 10:05 AM, Timon Gehr wrote:
This is a misunderstanding. The __mutable DIP will define the set of allowed
program rewrites based on const/immutable/pure. Then code that uses __mutable
must remain correct when they are applied. This achieves two things: it clearly
defines the semantics of const/immutable/pure and (the possibility of) __mutable
will not be an optimization blocker.
I'll get back to this once I have finished the tuple DIP implementation.
This is good news. I'm looking forward to both of them.
