Uros Bizjak writes:
> Attached is the patch I have committed.
Thanks for taking care of that.
> (BTW: Do you have any idea on what to do with excessive memory usage
> in chan/select2.go? )
At this point I don't. It's sort of peculiar. Sending an int on a
channel should not use any memory.
On Tue, Jan 31, 2012 at 8:36 PM, Ian Lance Taylor wrote:
>> There is no need for a panic in test/nilptr.go if array doesn't get
>> allocated in first 256 meg of memory. The compiler has nothing to do
>> with this.
>
> This is true but this does not seem like the right patch.
> I think I would pr
Uros Bizjak writes:
> There is no need for a panic in test/nilptr.go if array doesn't get
> allocated in first 256 meg of memory. The compiler has nothing to do
> with this.
This is true but this does not seem like the right patch.
> Index: test/nilptr.go
>
Hello!
There is no need for a panic in test/nilptr.go if array doesn't get
allocated in first 256 meg of memory. The compiler has nothing to do
with this.
Index: test/nilptr.go
===
--- test/nilptr.go (revision 183732)
+++ test/n
