> But in my experimenting the overhead of calling `go test` is quite high:
`go test -count 1 ; go test -count 1 ` is 50% slower than `go
test -count1 `.
Oops, I forgot to take parallelism into account. Once I do, it drops to
30% slower (which is still significant):
% time go test ./pkg/...
[
Hello,
I wish to call some Windows functions, some of which take pointers to types
which themselves contain pointers. For this purpose I intended to use
golang.org/x/sys/windows/mkwinsyscall.go and not cgo; in past I have
implemented
a package that uses WASAPI by generating "syscall" bodies with
Hi, Nicola,
Great to see the SFTPGo author is also here!
Actually I was checking how to integrate FTP with SeaweedFS. It will be
great to get some insight from you:
1) Really dumb question. Do people still use FTP? I have not used it myself
for a long time.
2) How reliable/mature/performant
On Mon, Oct 26, 2020 at 12:29 AM Oliver Smith <
oliver.sm...@superevilmegacorp.com> wrote:
> This pattern/idiom is very un-golike in that it's an eyesore, and one of
> the hardest things I've found to teach people new to trying to read go code.
>
FWIW, I definitely disagree that this is somehow "
If it isent too much work then I would keep safari support even if it would
be less performant. But Apple is forcing the usage of webkit on ios and
intentionally crippling webkit at the same time. So we might just have to
cut of Safari till the antitrust suits go through...
On Sunday, 25 Octob
Looking at how C++ has chosen to provide it's users with generators served
as a bit of a wake-up call for me on how we implement them in Go. We write
them backwards:
```go
func getPositiveOdds(numbers []int) <-chan int {
channel := make(chan int)
go func () {
defer close(channel)
Hi,
I just added Azure Blob Storage backend support to SFTPGo.
If you are interested in this feature you are encouraged to try it out and
report any issues you encounter.
You can easily test the latest SFTPGo Git revision using the "edge" or
"edge-alpine" tag for the Docker image or you can do
> So please feel free to write down your thoughts and ideas!
My recommendation would be less performant wasm for Safari where it is easily
maintained. Otherwise drop Safari support almost out of principle. Leaving
users vulnerable to script kiddie attacks by monopolising Safari engine use AND
Hi all,
I'm trying to upgrade from go 1.14.6 to 1.15.2 (soon to 1.15.3).
I have a folder under $GOPATH not related to any golang project that has
permissions (700) only to the owner/root user (I'm using linux/centos-8)
and when I issue a go install ./... on my project root folder
($GOPATH/src/g
I'd put all that C-calling code in ONE goroution, with
runtime.LockOSThread, and send commands to this thread through a channel,
with a receiver chan for response, too.
This way only one goroutine needs LockOSThread, and only that pays the
memory penalty.
If it becomes the bottleneck, you can ea
Thanks Ian
I found out that some libraries use thread-local storage
I understood that it should be called runtime.LockOSThread() in my go
routine because each C function in for-loop can run on different thread
I have one more question.
If I called runtime.LockOSThread(), should I also call
runt
On Sat, Oct 24, 2020 at 7:30 PM JuanPablo AJ wrote:
> I have some doubts related to the HTTP client.
>
First, if you have unexplained efficiency concerns in a program, you should
profile and instrument. Make the system tell you what is happening rather
than making guesses as to why. With that s
There currently is an open discussion on browser compatibility for Go-based
WASM that I believe could use a wider audience:
https://github.com/golang/go/issues/28360. It could have a big impact on
the usefulness of Go for targeting the future web (such as supporting the
Safari web browser, or n
13 matches
Mail list logo
