Re: [go-nuts] Is there any way to force Go to call asm function using register-based arguments?

Ok Google, so one can use `-asmflags=-compiling-runtime` to work around this limitation. The resulting speed-up can be well worth it. On Saturday, 1 July 2023 at 22:46:03 UTC+7 opennota wrote: Any update on this? I wanted to use the register-based calling convention as well and got "ABI

[go-nuts] CPU usage increasing day by day because of Cron

I am running a cron whose code is written in Golang ,and i am using mongoDb(version -4.4) as database, the cron runs after every 5 minutes of interval, i have been noticing that when i start the cron

Re: [go-nuts] [RFC] Yet another proposal for Go2 error handling

On Wednesday, June 28, 2023 at 1:30:41 PM UTC-4 Sven Anderson wrote: I think for what you want to do you don't need any language extension. On Sunday, July 2, 2023 at 2:04:29 PM UTC-4 Harri L wrote: *The sample block below is what we can have without any language updates.* Many times when

Re: [go-nuts] slog - potentially broken test

It appears to be quoting the source string because your build path contains a space. Apparently the slog authors didn't anticipate that case. I would open an issue. They may want to change the code to always quote the source file string or they may simply want to update the regex in the unit test

[go-nuts] slog - potentially broken test

When attempting to build from source on Windows, a test in slog fails for me every time. Am I doing something wrong or should I file an issue and submit a PR to improve this test? The issue seems to be the "source" being surrounded by quotes. See details below. *Test output *(from running

Re: [go-nuts] [RFC] Yet another proposal for Go2 error handling

On Sun, 2023-07-02 at 10:41 -0700, Jeremy French wrote: > Scrolling in code is bad - a necessary evil, obviously, but evil > nonetheless.  Vertical scrolling is bad because it causes what we > were looking at to move and our eyes have to track and/or reacquire > what we were looking at.  It's

Re: [go-nuts] [RFC] Yet another proposal for Go2 error handling

The sample block below is what we can have without any language updates. I will let you decide your thoughts about its readability, but please note that even the error strings are built automatically—error propagation with error traces, of course. Deferred error handling seems to clarify

Re: [go-nuts] [RFC] Yet another proposal for Go2 error handling

Scrolling in code is bad - a necessary evil, obviously, but evil nonetheless. Vertical scrolling is bad because it causes what we were looking at to move and our eyes have to track and/or reacquire what we were looking at. It's obviously possible, but on the micro-scale it's expensive when