Thanks Lucas, for reporting this bug!

As it looks, yaegi currently does not support go-1.18 properly[1] - atleast
support for generics is missing.
I could maybe circumvent these tests somehow but that does not look the most
optimal thing to do atleast for now. So I will get the ball rolling once 
go-1.19 is out
and yaegi adds proper support.

That said, looking at these bug reports I really feel we(go-team maints)
should do proper rebuilds and testing before going YOLO on updating to new 
golang version. Bumping
golang-defaults in a single shot causes problems like these.

[1]: https://github.com/traefik/yaegi/issues/1363

Regards,
Nilesh

Attachment: signature.asc
Description: PGP signature

Reply via email to