It would be great if there were a universal standard location in the user's
$HOME directory that is already on the PATH, because that always trips up new
users when starting to use a CLI.
But that does not appear to be the case on the mac -- this seems to be what a
default user gets, at least
The Go compiler is not very good at eliminating redundant copies of large
temporaries (structs with many fields, or arrays with length>1).
On Tuesday, July 13, 2021 at 2:51:32 PM UTC-7 buro...@gmail.com wrote:
> https://go.godbolt.org/z/G8K79K48G - small
> https://go.godbolt.org/z/Yv853E6P3 -
https://go.godbolt.org/z/G8K79K48G - small
https://go.godbolt.org/z/Yv853E6P3 - long
>go version go1.16 windows/amd64
On the local machine i am executing go tool compile -S main.go > main.s
in the second case, I see that the compiler sees here a local variable
entering the code. Why is this
With recent changes to go install, we now have an official, module-aware
way to locally build and install Go tools. This is a great step, but
I wonder if some renewed consideration should be made to where the tools
are installed.
As I'm sure you all know, go install puts binaries in $GOPATH/bin
On Tue, Jul 13, 2021 at 1:29 PM Kristoffer Semelka wrote:
>
> I noticed that word sized datatypes can be stored directly in the data field
> of an iface/eface, but I'm confused on how marking works with these kinds of
> inline cases. I checked the mark routines in the runtime/gcmark.go and
>
I noticed that word sized datatypes can be stored directly in the data
field of an iface/eface, but I'm confused on how marking works with these
kinds of inline cases. I checked the mark routines in the runtime/gcmark.go
and couldn't find special casing for interfaces. How does the runtime know
Hello gophers,
We have just released go1.17rc1, a release candidate version of Go 1.17.
It is cut from release-branch.go1.17 at the revision tagged go1.17rc1.
Please try your production load tests and unit tests with the new version.
Your help testing these pre-release versions is invaluable.
I knew I had seen something on that. :)
I guess Go doesn’t need a compacting collector if it can allocate most objects
on the stack to avoid fragmentation.
> On Jul 13, 2021, at 4:34 AM, Brian Candler wrote:
>
>
>> On Tuesday, 13 July 2021 at 03:52:24 UTC+1 bai...@gmail.com wrote:
>> Hi, I
On Tuesday, 13 July 2021 at 03:52:24 UTC+1 bai...@gmail.com wrote:
> Hi, I wrote a test program, which tests when GC starts to return heap
> space to OS.
> Here's the code: https://paste.ubuntu.com/p/jxHqDnsM2T/
>
> But I've waited for a long time and haven't seen the RSS memory reduced. I
>
