[go-nuts] Golang subversion vcs

I see the latest (Go 1.17.X) releases support Subversion modules but I cannot figure out how to get the `go get` command to pull in a tagged subversion module. Subversion repo layout - tags - contracts - configcontracts - v2.8.1 - trunk - contracts - configcontracts - g

[go-nuts] Re: gopls performance question

To follow up, I did submit an issue and it is related to a bug in gopls: https://github.com/golang/vscode-go/issues/299 -- 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 ema

[go-nuts] Re: gopls performance question

seconds in VSCode. I am using VSCode 1.46.1 on Linux. Could this in some way be a VSCode issue instead of gopls? On Friday, July 3, 2020 at 3:43:53 PM UTC-4, Luke Mauldin wrote: > > I have a Go project that is relatively small in terms of number of files > (less than 30) but some Go files

[go-nuts] gopls performance question

I have a Go project that is relatively small in terms of number of files (less than 30) but some Go files have auto-generated code that makes them relatively large - some between 3-4 MB. I counted the SLOC using https://github.com/hhatto/gocloc and it reports about 61K lines of code and 40K li

[go-nuts] Re: Many instances question - shared library

I agree that it is not a scalable architecture but unfortunately it is a large third party application the business depends on and it cannot be rewritten. Option 3 to use grpc is a good idea but unfortunately won’t work either because the Go shared library invokes C function calls back into the

[go-nuts] Re: Many instances question - shared library

The multiple instances are required to due to way the 3rd party application works. In brief, it creates a new process for each user connection and then each new process dynamically load the Go shared library to provide C extension points. -- You received this message because you are subscribed

[go-nuts] Many instances question - shared library

I have deployed a Go shared library on Linux that exposes C functions as extension points for a 3rd party application and is loaded dynamically at runtime. The 3rd party application then invokes "C" functions (which are backed by Go) and that is all working as expected. However, due to the nat

[go-nuts] Build with C dependencies

I have a Go program that I need to link against multiple C libraries in order to compile. I am setting the CFLAGS and LDFLAGS through #cgo directives which works nicely. My problem is that I would like to run my go builds (and test, etc...) inside a docker container so I can put the C include

[go-nuts] Windows cgo complier

Can someone please tell me what the golang team uses as the reference windows x64 compiler? I have heard references to mingw64 but it would be helpful to know the exact version they are using for their unit tests on Windows. I am experiencing different cgo windows behavior in 1.10 than 1.9.3 and

[go-nuts] Go Windows vs Linux networking stack differences

("tcp", ":8080), etc.. but I would like to know if there are underlying network stack differences in the Go standard library that will cause different performance characteristics between the two OSes? Luke Mauldin -- You received this message because you are subscribed to th

[go-nuts] Win 32bit calling convention

I am using the steps as detailed at the bottom of this issue https://github.com/golang/go/issues/11058 to create a Go shared library on Windows exposing C function. Right now it is all working compiling in X64. If I also want to make an X32 version of my library, I know I will have to set som

[go-nuts] C Syscall Memory Code Review

Can you please review the code here: https://play.golang.org/p/Yk6nqHhtTo This forms the basis of a "memory" package which I am using on Windows to do interoperability with some C APIs. These existing C APIs sometimes take/return a C-null terminated pointer and sometimes they take/return a poi

Re: [go-nuts] Go string to uintptr

Thank you for the help, that worked. I don't want to use cgo directly because of the compile overhead and because cgo prevents debugging on Windows. Another question, if there is a C function with the declaration: void returnOutCString(char ** out) I can call the function using: var retPtr uns

[go-nuts] Go string to uintptr

I am on Windows and I am using the syscall package to call C functions exposed in windows dlls. I am trying to call a C function that accepts a "const char*" parameter. How do I convert a Go string to a uintptr that I can use in (p *LazyProc) Call(...)? I have tried several different approac

Re: [go-nuts] Cgo Pointer Arithmetic

tions into memory safe Go slices that will then be used throughout the Go program. On Wednesday, August 31, 2016 at 5:26:27 PM UTC-5, Ian Lance Taylor wrote: > On Wed, Aug 31, 2016 at 2:06 PM, Luke Mauldin > wrote: > > I modified my example based on the code example you gave

Re: [go-nuts] Cgo Pointer Arithmetic

entries? If so, how great is that penalty? On Wednesday, August 31, 2016 at 3:17:30 PM UTC-5, Ian Lance Taylor wrote: > On Wed, Aug 31, 2016 at 12:47 PM, Luke Mauldin > wrote: > > > > I have questions about pointer arithmetic illustrated by this Play > example: > >

[go-nuts] Cgo Pointer Arithmetic

I have questions about pointer arithmetic illustrated by this Play example: https://play.golang.org/p/-cZteTY_M2 Questions: 1) Is this the best way to do pointer arithmetic in Go to process a C array and convert it to a Go slice? 2) Go vet gives an error on line 18 but doesn't give much informa