Support Go version `1.18beta1`
See original GitHub issueDescription: Support go-version
1.18beta1
(or have it as 1.18.0-beta1
/1.18.x
)
Justification: We want to experiment with Go 1.18 beta1 fuzzing and generics features, and it adds extra bloat in our CI configuration to install Go 1.18beta1 for now.
Are you willing to submit a PR? No; I have looked a bit through the code but it looks like something would need to be added to the go-versions
repository which we cannot create PRs to.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:5
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Go 1.18 Beta 1 is available, with generics
Go 1.18 Beta 1 adds built-in support for writing fuzzing-based tests, ... Go 1.18 Beta 1 contains an expanded go version -m command, ......
Read more >Add Go 1.18 support · Issue #1092 · gopherjs ... - GitHub
18 branch to master today, and I am planning to tag a 1.18beta1 release once #1137 is merged. This change yields a noticeable...
Read more >Go Generics Debut in Go 1.18 Beta 1 - InfoQ
The latest beta release of Go, Go 1.18 beta 1, finally introduces support for generics programming using parametrized types, a long-awaited ...
Read more >Major update to the golang-set repo now supporting generics ...
With the release of Go 1.18 beta1 build, I have reworked this library to utilize generics within the code. There are a few...
Read more >Change log : golang-1.18 package : Ubuntu - Launchpad
Change log for golang-1.18 package in Ubuntu ... contains flags that might make host object files that the internal linkers ELF reader does...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi, @qdm12!
I couldn’t reproduce your problem. Please check my WF.
I use
Could you please provide some repro steps or public repo where your problem occurs?
A recommendation for the future, it may be worth adding a note to the
Supported version syntax
section of the readme that unstable versions needstable: false
. Or potentially adding an inputs table with both the format information and the stable input described.I was personally looking for the way to import the beta, and missed the “Matching an unstable pre-release” example adding said input.