I agree with you 100%. The 'go install' step that creates the shared
runtime library should only be done by
root.
On the other hand, there's no reason I can see for the 'go build' step to
write anything at all
into /usr/local/go. But that's clearly happening. That's one of the causes
of this pr
> So, the solution to problem #1 is to make sure a normal user can create
/usr/local/go/pkg/linux_amd64_dynlink and files in and underneath it.
While this is fine as a proof of concept and to diagnose the situation, I
don't think that it can be called good advice to make /usr/local writeable
to
I'm not sure there really is a "reason", per se. The language could just as
well have been designed not to require parentheses around the return types
(at least I see no parsing ambiguity with that, though there might be) or
designed to require parentheses in the return statement. It probably just
Hey all, I figured it was time to move to a "modern" language and I thought
I'd give go a try. So far, I'm really enjoying it. I'm just getting started
and I had a question about parentheses. Though, I guess it's really about
how go parses lines of code and what counts as a delimiter.
Anyway, i
