Go-retry Alternatives

Similar projects and alternatives to go-retry

go

2,067 119,564 10.0 Go go-retry VS go

The Go programming language
swift-evolution

124 15,003 9.7 Markdown go-retry VS swift-evolution

This maintains proposals for changes and user-visible enhancements to the Swift Programming Language.
WorkOS

workos.com sponsored

The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
go101

41 5,382 7.2 HTML go-retry VS go101

An up-to-date (unofficial) knowledge base for Go programming self learning
yaegi

39 6,596 5.6 Go go-retry VS yaegi

Yaegi is Another Elegant Go Interpreter
go-sumtype

11 403 0.0 Go go-retry VS go-sumtype

A simple utility for running exhaustiveness checks on Go "sum types."
enumer

6 369 2.3 Go go-retry VS enumer

A Go tool to auto generate methods for your enums (by dmarkham)
yaegi-template

5 31 0.0 Go go-retry VS yaegi-template

Discontinued Use yaegi as a template engine.
InfluxDB

www.influxdata.com sponsored

Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
sqlread

1 48 5.5 Go go-retry VS sqlread

SQL Dump Parser - Query MySQL Dumps Directly without loading them into MySQL

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better go-retry alternative or higher similarity.

Suggest an alternative to go-retry

go-retry reviews and mentions

Posts with mentions or reviews of go-retry. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-02-04.

What I'd like to see in Go 2.0
11 projects | news.ycombinator.com | 4 Feb 2022

I was also curious so I picked a likely-looking project on his github and indeed found an attempt to handle a channel "deterministically" at https://github.com/sethvargo/go-retry/blob/main/retry.go#L51
Honestly the whole first select seems redundant; any code that relies on this is broken. But OK, maybe you do have some strange performance case where this matters? In that case the whole thing could be more succinctly solved by looping on `for ctx.Err() == nil` instead of infinitely.
It also leaks the timer until it fires if the context cancels, which seems like it would be more of a practical performance problem than any overhead to the additional elect.