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
I have written a small console application that has package main at the top
and the program looks just like another console that runs successfully. On
both mac and windows I am getting a message stating the executable created
is not executable. Has anyone else seen this error? I am on go 1.12
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
