re the solution.
>
> On Sunday, 4 August 2019 16:50:45 UTC+1, Allan Edwards wrote:
>>
>> I am sorry, ignore me, I figured it out. Problem in goland
>> configuration. Thanks for the response.
>>
>> On Sunday, August 4, 2019 at 10:44:12 AM UTC-5, Alexander Kapsh
I am sorry, ignore me, I figured it out. Problem in goland configuration.
Thanks for the response.
On Sunday, August 4, 2019 at 10:44:12 AM UTC-5, Alexander Kapshuk wrote:
>
> On Sun, Aug 4, 2019 at 6:37 PM Allan Edwards > wrote:
> >
> > I have written a small console
might be doing something weird on the build.
On Sunday, August 4, 2019 at 10:44:12 AM UTC-5, Alexander Kapshuk wrote:
>
> On Sun, Aug 4, 2019 at 6:37 PM Allan Edwards > wrote:
> >
> > I have written a small console application that has package main at the
> top and the
1.12.7.
Thanks!!!
Allan
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web vi
Wow, thanks for responding guys. So I ran my exe on linux without goland
and bam the readstring blocked as needed. For some reason the ReadString
call is not blocking inside of goland. It seems like a great IDE but I
found a weird bug. On the Windows side the ReadString blocks inside of
go
I run a demo program to learn sync.NewCond：
package main
import (
"fmt"
"sync"
"time"
)
var locker = new(sync.Mutex)
var cond = sync.NewCond(locker)
func test(x int) {
cond.L.Lock()
cond.Wait()
fmt.Println(x)
time.Sleep(time.Second * 1)
cond.L.Unlock()
}
func main(
Yes, you're right.
Thannk you.
在 2017年3月8日星期三 UTC+8上午12:05:33，Howard C. Shaw III写道：
>
> io.Copy is going to read from one stream and write to the other, until the
> read stream is closed. "Copy copies from src to dst until either EOF is
> reached on src or an error occurs." So until you close
