[go-nuts] [GOLLVM] Running LLI on LLVM Bitcode Fails with Recommended Setting

Hello, I am trying to follow this commit of gofrontend: 140917: runtime: hack to make LLVM's lli work . For LLVM, GO-LLVM, LIBFFI and LIBBACKTRACE I am following the recommended commits as well: GOLLVM_COMMIT=3452ec6bebaa1b432aabed1991

Re: [go-nuts] go1.21.0 panics when loading plugin

On 8/8/23 18:16, Kurtis Rader wrote: Did you also recompile the plugin with the new Go toolchain? It's a requirement of plugin support that the main program and all plugins be compiled with the same toolchain. Yes, the loading program and the module were both compiled with the same toolchain.

Re: [go-nuts] What happened to sep in errorrs.join

I think you can do what you want with `HandlerOptions.ReplaceAttr`. It is given every attribute, even the message. It can't change the group names, though, and those can have newlines. On Tuesday, August 8, 2023 at 5:47:38 PM UTC-4 Ian Lance Taylor wrote: > [ + jba ] > > On Tue, Aug 8, 2023 at

Re: [go-nuts] What happened to sep in errorrs.join

[ + jba ] On Tue, Aug 8, 2023 at 4:24 AM Joseph Lorenzini wrote: > > Thanks that was very helpful. As for your point about slog, yes a custom > handler could but I am using the library json handler. > > I suppose the proper way to frame my problem is that I am using the slog > library handler a

Re: [go-nuts] go1.21.0 panics when loading plugin

Did you also recompile the plugin with the new Go toolchain? It's a requirement of plugin support that the main program and all plugins be compiled with the same toolchain. On Tue, Aug 8, 2023 at 11:12 AM Bernd Fix wrote: > After switching from go1.20.7 to go1.21.0 one of my applications > compi

[go-nuts] go1.21.0 panics when loading plugin

After switching from go1.20.7 to go1.21.0 one of my applications compiles without warnings or errors, but fails at run-time with the following panic when loading a plugin: panic: regexp: Compile(`^([\w./]+)/((?:\w+)|[*])(.+)?$`): error parsing regexp: invalid escape sequence: `\w` goroutine

[go-nuts] Re: Go 1.21.0 is released

On Tue, Aug 8, 2023 at 5:24 PM wrote: > We have just released Go 1.21.0. > > To find out what has changed in Go 1.21, read the release notes: > https://go.dev/doc/go1.21 > > You can download binary and source distributions from our download page: > https://go.dev/dl/#go1.21.0 It looks like the d

[go-nuts] Go 1.21.0 is released

Hello gophers, We have just released Go 1.21.0. To find out what has changed in Go 1.21, read the release notes: https://go.dev/doc/go1.21 You can download binary and source distributions from our download page: https://go.dev/dl/#go1.21.0 If you have Go installed already, an easy way to try go

Re: [go-nuts] What happened to sep in errorrs.join

Thanks that was very helpful. As for your point about slog, yes a custom handler could but I am using the library json handler. I suppose the proper way to frame my problem is that I am using the slog library handler and I do not want new lines in the message or keys. Would the go team would be o

[go-nuts] Re: [ann] knoa (dealing with unstructured data)

You can check it in action here, https://go.dev/play/p/LCkzZSiXbo9 El lunes, 7 de agosto de 2023 a las 23:12:27 UTC+2, Iván Corrales Solera escribió: > I'm so happy to announce the very first release of *knoa > * > > The goal of knoa is to provide *a handy