I decided to place them all in one place for containment.
I used the names from envvars to get a simple answer to a simple question:
*where
is GOROOT?*, *in go/root*.
GOMODCACHE picks up GOPATH.
GOTOOLDIR picks up GOROOT.
GOTMPDIR defaults to system's tmp dir, I'm fine with that.
On Wednesday,
On Tue, Dec 8, 2020 at 11:11 PM xie cui wrote:
>
> https://github.com/golang/go/blob/master/src/runtime/proc.go#L248-L251
> why these codes, it seem is unnecessary?
Those lines are there to help new ports. If the `exit` function isn't
working right, it might return. If the signal handler isn't
https://github.com/golang/go/blob/master/src/runtime/proc.go#L248-L251
why these codes, it seem is unnecessary?
--
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
To clarify the go compiler toolchain is a trivial tree. Compared to
most other mainstream languages and compilers, it's not scattered to
different subtrees. I believe quite some effort went into that to stay
that way.
When using the go compiler toolchain some directories are used for
caching
Hello Friends
I am trying to build an WebApp, and this is my first one. do we need to use
external router like gorilla/mux for routing ?
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails
Thanks a lot, Shulhan.
On Wednesday, December 9, 2020 at 1:03:01 PM UTC+8 Shulhan wrote:
>
>
> On Wed, 9 Dec 2020, 11:42 xiangd...@gmail.com,
> wrote:
>
>> Hi all,
>>
>> I'm wondering if any linter, or is it practical to make one, checks
>> whether a go module's code change conforms the
Yes, there is no requirement to manage the envvars. I personally believe
there is a requirement to know about them, though.
I read the installation doc, I think there's a hang up on your part on this
one.
The default go tree is scattered different places, beside the obvious
trivial tree you're
On Wed, 9 Dec 2020, 11:42 xiangdong...@gmail.com,
wrote:
> Hi all,
>
> I'm wondering if any linter, or is it practical to make one, checks
> whether a go module's code change conforms the minimal version selection
> rules, say linter warns a v2 is needed if incompatible changes to APIs are
>
Hi all,
I'm wondering if any linter, or is it practical to make one, checks whether
a go module's code change conforms the minimal version selection rules, say
linter warns a v2 is needed if incompatible changes to APIs are introduced
in the current change under linting?
--
You received this
I couldn't get the information I needed when I posted this question on a
couple of forums, so I've posted a detailed explanation of how to use
packages and modules with git repositories on private servers
I tried to play with go runtime to seamlessly add memory (bytes, objects,
allocation calls) tracing into any arbitrary go code. Check it out in the
repo https://github.com/1pkg/gotcha and in blog post
https://1pkg.github.io/posts/lets_trace_goroutine_allocated_memory/.
--
You received this
There is no requirement to manage these variables or to know about them,
even if you don't use the installer.
I never use the installer and I've never needed to check on those
environment variables.
(The installation documentation is short and complete, maybe you should
check it out again.)
The
I don't use an installer. I set GOROOT/bin manually. And the rest follows.
Easy to remember, nothing to forget.
On Tuesday, December 8, 2020 at 6:28:50 PM UTC+2 Gergely Födémesi wrote:
> On 12/8/20, Dumitru Ungureanu wrote:
> > Paths in symmetry with the environmental
> > variables: GOROOT is
On 12/8/20, Dumitru Ungureanu wrote:
> Paths in symmetry with the environmental
> variables: GOROOT is go/root, GOPATH is go/path, GOBIN is go/bin. GOCACHE is
> go/cache, GOENV is go/env.
> Bonus points: modules in go/modules.
Why do you need to manage them explicitly? When do you need to look
Paths in symmetry with the environmental
variables: GOROOT is go/root, GOPATH is go/path, GOBIN is go/bin. GOCACHE is
go/cache, GOENV is go/env.
Bonus points: modules in go/modules.
On Tuesday, December 8, 2020 at 4:45:06 PM UTC+2 Gergely Födémesi wrote:
> On 12/7/20, Dumitru Ungureanu
Hi! I installed Go via sources
$ go version
go version devel +9c91cab0da Tue Dec 8 01:46:45 2020 + darwin/arm64
got better performance than I had with my aging Core i5 4670k, etc, this
was expectable, no surprises here.
But, there's an issue. When I call `go get`, `go install`, etc via
On 12/7/20, Dumitru Ungureanu wrote:
...
> I'm currently using this directory tree for golang.
...
What do you mean when you write "golang"?
Why is https://golang.org/doc/install not good enough for the go compiler?
--
You received this message because you are subscribed to the Google Groups
Hello,
Thanks for the note.
I am still not completely sure what the problem is.
You wrote:
| I found
|
| // triple: i686-pc-linux-gnu
| static const CpuAttrs attrs1[] = {
| // first entry is default cpu
| { "i686", "+cx8,+x87"},
|
| and (inside the hashmap)
|
| { "yonah",
Hi,
On Tue, Dec 8, 2020 at 1:19 AM 'Charles Hathaway' via golang-nuts <
golang-nuts@googlegroups.com> wrote:
> Hi all,
>
> I'm looking for a good study/quantitative measure of how well-written Go
> code looks compared to other languages, such as Java, when it comes to test
> coverage. In
19 matches
Mail list logo
