Re: [go-nuts] Need help: Calling panic() is corrupting system stack

Hi Ian, You are correct. The following test case is failing. I commented out the code to make sure whether my analysis is correct or not. Definitely, you people are experts. What could be the best fix for this issue? If you can help then that is really helpful. === RUN TestCallbackPanicLoop sig

[go-nuts] Disable AVX, AVX2, AVX-512, SSE support while building a go binary

Hi I want to build a simple go binary that prints "hello world" but disablesthe use of all optional instruction set extensions e.g disable AVX, AVX2, AVX-512, SSE support . Thanks Aditi -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsub

Re: [go-nuts] Need help: Calling panic() is corrupting system stack

On Tue, Apr 4, 2023 at 9:20 PM mariappan balraj wrote: > > In my test case, I have tried, Go-->C-->Go->panic() only. You can run a bunch of cgo tests by running "go test" in the directory $GOROOT/misc/cgo/test. Ian > On Wed, Apr 5, 2023 at 3:35 AM Ian Lance Taylor wrote: >> >> On Mon, Apr 3,

[go-nuts] Re: watching for directory/file changes using golang/windows

On Sunday, July 1, 2012 at 2:33:23 PM UTC+3 Bhaskar teja Yerneni wrote: Hi, I have been working on a Javascript and css minification and concatenation server using go 1.0.2 https://github.com/prudhviy/goclubby/blob/master/goclubby.go wondering if golang1.0.2 supports directory and file chang

[go-nuts] Re: watching for directory/file changes using golang/windows

On Sunday, July 1, 2012 at 2:33:23 PM UTC+3 Bhaskar teja Yerneni wrote: Hi, I have been working on a Javascript and css minification and concatenation server using go 1.0.2 https://github.com/prudhviy/goclubby/blob/master/goclubby.go wondering if golang1.0.2 supports directory and file chang

[go-nuts] OpenApi generated Gin application example

Hi guys, Does anybody know of a good example of how to structure an OpenApi generated go-gin-server. It would be nice to be able to regenerate the files again without loosing to much work. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To un

Re: [go-nuts] Redfining loop variable semantics - what's the plan?

Based on studying large bodies of existing code, you should be about 25x more scared right now that there's an undetected bug in your code from the existing semantics -- especially if you haven't written many tests. If this change does cause a failure in existing code, we have a tool to help i

[go-nuts] Re: RLIM_INFINITY for loong64 has a special type.

The issue seems clear. syscall.RLIM_INFINITY for loong64 does not have a special type. syscall.RLIM_INFINITY for loong64 (0x) is a reasonable ordinary value for type rlim_t (uint64). Prometheus has a bug. --- The Open Group Base Specifications Issue 7, 2018 edition https://p