gtools VS iter

Compare gtools vs iter and see what are their differences.

gtools

Generic tools for go 1.18+ (by Malefaro)

iter

Package iter provides generic, lazy iterators, functions for producing them from primitive types, as well as functions and methods for transforming and consuming them. (by mtoohey31)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
gtools iter
2 2
1 32
- -
0.0 5.2
about 2 years ago about 2 months ago
Go Go
- BSD 3-clause "New" or "Revised" License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

gtools

Posts with mentions or reviews of gtools. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-01-10.
  • iter: Generic, lazy iterators for Go 1.18
    6 projects | /r/golang | 10 Jan 2022
    Looks good Do you benchmark it vs for loop? Recently I am wrote pretty similar lib but using functions for all(filter, ForEach etc): gtools Maybe you will find something for yours lib

iter

Posts with mentions or reviews of iter. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-01-10.
  • iter: Generic, lazy iterators for Go 1.18
    6 projects | /r/golang | 10 Jan 2022
    I've been working on an iterator package for Go 1.18. Here's a quick snippet:
    6 projects | /r/golang | 10 Jan 2022
    The reason why I decided on the inner/outer architecture was because interface objects can't be used as recievers to methods (as far as I understand). As a result, my initial implementation, which didn't have this structure, was limited to functions instead of methods, which made code where iterator methods were chained extremely unreadable, since it was difficult to tell which order they were being applied in. It's a tradeoff, but I think the readability might be worth it. Do you have any ideas for alternative workarounds?

What are some alternatives?

When comparing gtools and iter you can also consider the following projects:

iter - iter is a generic iterator library for Go

go-generic - A collection of experiments using Go Generics coming out in Go 1.18

go-iterator - Go 1.18 generics iterator experiment

go - The Go programming language

Lazytainer - Docker container lazy loading

gods - GoDS (Go Data Structures) - Sets, Lists, Stacks, Maps, Trees, Queues, and much more