You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As much as I don't like breaking changes I think we better follow the upstream here, it's a standard now and being off this standard makes the library inconvenient to use. But the change is quite radical and we need new method/function names at the same time I think, otherwise people will upgrade SDK and not notice this change until it breaks in some way.
with Go 1.23, iterators became extremely powerful. We already had some even before
sometimes iterator cannot be used with
for range
directly due to breaking condition. For example, https://pkg.go.dev/github.com/nspcc-dev/neofs-sdk-go@v1.0.0-rc.13/netmap#NodeInfo.IterateNetworkEndpoints breaks ontrue
whilefor
requiresfalse
. This can be solved via wrapper:i propose to provide iterators with inverted behavior
The text was updated successfully, but these errors were encountered: