On Thu, Aug 17, 2023 at 08:38:48PM +0300, Nir Soffer wrote:
> > > > I'm not sure what is the purpose of this test - requiring the Go
> > version is
> > > > good
> > > > enough since the code will not compile with an older version. EVen if
> > it
> > > > would,
> > > > it will not compile without un
On Tue, Aug 15, 2023 at 9:53 PM Eric Blake wrote:
> On Mon, Aug 14, 2023 at 01:43:37PM -0500, Eric Blake wrote:
> > > > +++ b/golang/configure/test.go
> > > > @@ -25,8 +25,19 @@
> > > > import (
> > > > "fmt"
> > > > "runtime"
> > > > + "unsafe"
> > > > )
> > > >
> > > > +
On Mon, Aug 14, 2023 at 01:43:37PM -0500, Eric Blake wrote:
> > > +++ b/golang/configure/test.go
> > > @@ -25,8 +25,19 @@
> > > import (
> > > "fmt"
> > > "runtime"
> > > + "unsafe"
> > > )
> > >
> > > +func check_slice(arr *uint32, cnt int) []uint32 {
> > > + /* We re
On Sun, Aug 13, 2023 at 08:38:23PM +0300, Nir Soffer wrote:
> On Sat, Aug 12, 2023 at 12:18 AM Eric Blake wrote:
>
> > Go 1.17 or newer is required to use unsafe.Slice(), which in turn
> > allows us to write a simpler conversion from a C array to a Go object
> > during callbacks.
> >
> > +++ b/g
On Fri, Aug 11, 2023 at 04:16:09PM -0500, Eric Blake wrote:
> Go 1.17 or newer is required to use unsafe.Slice(), which in turn
> allows us to write a simpler conversion from a C array to a Go object
> during callbacks.
>
> To check if this makes sense, look at
> https://repology.org/project/go/ve
On Sat, Aug 12, 2023 at 12:18 AM Eric Blake wrote:
> Go 1.17 or newer is required to use unsafe.Slice(), which in turn
> allows us to write a simpler conversion from a C array to a Go object
> during callbacks.
>
> To check if this makes sense, look at
> https://repology.org/project/go/versions c
