Re: [go-nuts] where is GOROOT set?

You cannot have multiple packages (in your case main and goprorename) in one folder. This has nothing to do with modules. You must but these three files into two different folders based on their package declaration. You might want to work through https://go.dev/doc/code V. -- You received this

Re: [go-nuts] where is GOROOT set?

Thanks I've read the official tutorial and your create-module docs. They help, but I am still having issues getting this to hang together. I got the treesort example to work. Now I'm creating a new module, in a new subdirectory of my repositories and I've done the go mod init I have three go

Re: [go-nuts] Help debugging a SIGSEGV - "unexpected signal during runtime execution"

Hi Kurtis, Thanks for the response. To be clear this issue is the defect that I'm encountering. The issue was originally logged against *v1.0.0-beta4*. I am using *v1.0.0-beta6* but the defect has not been fixed. This defect occurs when calling

Re: [go-nuts] Help debugging a SIGSEGV - "unexpected signal during runtime execution"

It superficially looks like you're running the code from https://github.com/go-vgo/robotgo/blob/master/examples/key/main.go. However, The line number 136 in main.go in the backtrace doesn't make any sense since the example code from the project only has 134 lines. Did you modify the example code?

[go-nuts] []rune converter

Hello fmt.Println(ssr) show me right format of strin But in debug mode ssr =

[go-nuts] Help debugging a SIGSEGV - "unexpected signal during runtime execution"

Hi all, I'm using go version 1.19.4 darwin-amd64 I keep getting the following errors while trying to use a function from the robotgo package. I'm not experienced in C and could use some help trying to find the problem fatal error: unexpected signal during runtime execution [signal SIGSEGV:

[go-nuts] RE: glog - Security Vulnerability Report

Good morning, I'd like to follow up on the below email and whether the code that was flagged as a security issue will be looked into and fixed. I looked around at how another Go library fixed the issue, and this function may

Re: [go-nuts] Re: Interfaces for nested types with common structure

Code generation is the only option I can think of, perhaps with a top-level generic function to dispatch to the correct instance: https://go.dev/play/p/9nCZQsfOeyx Unfortunately the compiler doesn't accept this: func HelperFn[T interface{ *lib1.Baz | *lib2.Baz }](baz T) int { return