Comments (2)
In the Go ecosystem (as opposed to Java), staying close to the latest version of the Go runtime is the standard. I know of a few libraries that fully support the last 1-2 Go versions.
In this particular case, the previous version (at Go 1.13) still exists and can be pinned. The reason for this move is that we are preparing to upgrade everything in our internal infrastructure up to Go 1.17 to take advantage of how Go manages modules and dependencies.
If you require a lesser Go runtime than 1.17, please use the previous version of assertions
.
from assertions.
In the Go ecosystem (as opposed to Java), staying close to the latest version of the Go runtime is the standard.
I would disagree. Many popular foundation libraries are supporting Go 1.13 or even earlier.
The reason for this move is that we are preparing to upgrade everything in our internal infrastructure up to Go 1.17 to take advantage of how Go manages modules and dependencies.
Go modules have been well-supported since at least Go 1.15 (I believe even Go 1.14). There is nothing in Go 1.17 that I'm aware of that would require such a change.
from assertions.
Related Issues (20)
- should.ContainKey fails for int32 key HOT 1
- Assertions should allow an optional string with a better message HOT 3
- ShouldEqualJSON only supports JSON Objects at the root HOT 1
- [suggestion] loose slice equality HOT 1
- ShouldBeEmpty should warn if subject has no length
- ShouldEqualJSON does not work with json arrays HOT 4
- Problem running test HOT 1
- httptest.NewServer starts in background goroutine and causes data race when used with shouldNotBeNil (which depends upon string formatting) HOT 3
- Golang 1.16 beta 1: TestMapSortRendering fails on s390x HOT 7
- building error HOT 2
- Super small typo in documentation of ShouldNotBeBlank
- Versioning scheme changed backwards HOT 3
- TestMapSortRendering fails with go1.18 HOT 1
- map[int64]bool ShouldContainKey didn't work as expected HOT 4
- No function for comparing arrays and ignoring order HOT 4
- ShouldResemble can fail when there's no visual diff between the inputs HOT 1
- The module declares is incorrect HOT 2
- ShouldEqual no longer works with functions HOT 5
- Major version shall be bumped since v1.51.0 HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from assertions.