IssueRaiser

The problem is, as you say, it is quite doable, as long as you have internal access to all of the code .

The problem is, as you say, it is quite doable, as long as you have internal access to all of the code . There's no way to ensure that, for example, a function actually returns an immutable map, or actually doesn't modify a map passed to it. (And no, Collections.immutableMap doesn't.) (And then there are problems with the JVM bytecode as well - do you know you can pass 2 into a function expecting a boolean? And sometimes it'll get treated as true and sometimes as false? The JVM is "wonderful" like that.)

Posted by TheLoneWolfling on Jul 12, 2015, 8:54 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.5,500 issues0 comments

hackernews (Other)

The problem is, as you say, it is quite doable, as long as you have internal access to all of the code .

TheLoneWolflingJul 12, 2015, 8:54 PM

The problem is, as you say, it is quite doable, as long as you have internal access to all of the code . There's no way to ensure that, for example, a function actually returns an immutable map, or actually doesn't modify a map passed to it. (And no, Collections.immutableMap doesn't.) (And then there are problems with the JVM bytecode as well - do you know you can pass 2 into a function expecting a boolean? And sometimes it'll get treated as true and sometimes as false? The JVM is "wonderful" like that.)

Comments (0)

No comments yet. Start the discussion.

Comment on this issue