Hey Robert,
The problem is not reproducible in our test env but it occours on final
user. To make thing thougher is not even an application we develop directly
but is from one of our reseller, so we don't have direct access to the rest
of the codebase. Again I want to stress the main point of
Hi again :-)
I addressed feedback in CL https://go-review.googlesource.com/c/go/+/413594
Generators of ASM are now written in Go using template/text instead of
Python. Also added tests
Please review!
On Sun, Aug 7, 2022 at 11:59 AM Boris Nagaev wrote:
>
> Hi everyone!
>
> I sent CL
This most likely means your other code is corrupting the go runtime/heap/stack.
I would run other tests on this code exclusively (asan, etc).
> On Sep 10, 2023, at 12:54 PM, Danilo bestbug
> wrote:
>
>
> Hey TheDiveO, thanks for answering.
> My focus is not to hide the signal but I would
Hey TheDiveO, thanks for answering.
My focus is not to hide the signal but I would like to understand if this
behavior is wanted and in that case what we can do to avoid to have crash
report where the crashed thread does not run any of our "code".
Il giorno domenica 10 settembre 2023 alle
Maybe this SO Q with A might also help with further details:
https://stackoverflow.com/questions/47869988/how-does-cgo-handle-signals
On Friday, September 8, 2023 at 11:38:38 PM UTC+2 Danilo bestbug wrote:
> Ehy Ian, thanks for the response. Apology if I was not clear, I try to
> explain in a
The latest version of github.com/jba/templatecheck[0] supports templates
that cannot have type errors at execution time.
Once you've parsed your template `t` and all associated templates, call
ct, err := templatecheck.NewChecked[MyData](t)
If err == nil, then ct is a CheckedTemplate[MyData].
Hey, turns out you're right! I can call it like `f(a, "")`. I was naive to
believe Goland when it indicated an error. I need to submit a bug report to
JetBrains. That's good, because I feel this method is more reliable than
the second one. However, I'm still not a fan of the type assertion in
> https://go.dev/play/p/h5jzISRyTkF In this approach, I'm not fond of how I
must call the f function on line 30. Without specifying a type parameter,
the call fails to compile.
If I replace f[A](a, "") with f(a, "") it still works for me, in the
playground.
What go version are you using?
