Suggest specify go version for gnark, current go1.22.3 is preferred.

[readygo67]

In my project, the following error happen with go version v1.22.0 and disappear with version >= v.1.22.1.

runtime: g 7068: unexpected return pc for github.com/consensys/gnark/std/recursion/plonk.ValueOfVerifyingKey[go.shape.struct { github.com/consensys/gnark/std/math/emulated/emparams.fourLimbPrimeField },go.shape.struct { X github.com/consensys/gnark/std/math/emulated.Element[github.com/consensys/gnark/std/math/emulated/emparams.BN254Fp]; Y github.com/consensys/gnark/std/math/emulated.Element[github.com/consensys/gnark/std/math/emulated/emparams.BN254Fp] },go.shape.struct { P github.com/consensys/gnark/std/algebra/emulated/sw_bn254.g2AffP; Lines *github.com/consensys/gnark/std/algebra/emulated/sw_bn254.lineEvaluations }] called from 0x774ae84f2ff42d9f
stack: frame={sp:0x14143f4f730, fp:0x14143f50fb0} stack=[0x1403e380000,0x1403e480000)

I am not sure but guess this problem is related to below modification in https://go.dev/doc/go1.22.

reflect

The [Value.IsZero](https://go.dev/pkg/reflect/#Value.IsZero) method will now return true for a floating-point or complex negative zero, and will return true for a struct value if a blank field (a field named _) somehow has a non-zero value. These changes make IsZero consistent with comparing a value to zero using the language == operator.

The [PtrTo](https://go.dev/pkg/reflect/#PtrTo) function is deprecated, in favor of [PointerTo](https://go.dev/pkg/reflect/#PointerTo).

The new function [TypeFor](https://go.dev/pkg/reflect/#TypeFor) returns the [Type](https://go.dev/pkg/reflect/#Type) that represents the type argument T. Previously, to get the reflect.Type value for a type, one had to use reflect.TypeOf((*T)(nil)).Elem(). This may now be written as reflect.TypeFor[T]().

[ivokub]

Thanks for reporting. Seems indeed strange. Do you have an example of the circuit which leads to this error and what is the gnark version you're using? Currently we have fixed Go dependency to be 1.21 in go.mod to allow for non-bleeding edge Go versions, but the error still seems to be strange that appears with Go 1.22.0 and disappears with 1.22.1.