[racket-dev] Overly general types for mutable containers

On Sun, Jul 8, 2012 at 12:58 AM, Neil Toronto <neil.toronto at gmail.com> wrote:
> It runs directly counter to what I expect from immutable containers, which I
> use most of the time:

This is the problem.  Immutable containers are very different from
mutable ones, and your expectations shouldn't be expected to carry
over.  Mutability is a communications channel, not just a data storage
mechanism, and you should expect it to be different.
-- 
sam th
samth at ccs.neu.edu