add FuncFrog

[koss-null]

We want to ensure high quality of the packages. Make sure that you've checked the boxes below before sending a pull request.

• I have read the Contribution Guidelines
• I have read the Maintainers Note
• I have read the Quality Standards

Not every repository (project) will require every option, but most projects should. Check the Contribution Guidelines for details.

• The repo documentation has a pkg.go.dev link.
• The repo documentation has a coverage service link.
• The repo documentation has a goreportcard link.
• The repo has a version-numbered release and a go.mod file.
• The repo has a continuous integration process that automatically runs tests that must pass before new pull requests are merged.
• Continuous integration is used to attempt to catch issues prior to releasing this package to end-users.

Please provide some links to your package to ease the review

• forge link (github.com, gitlab.com, etc): https://github.com/koss-null/FuncFrog
• pkg.go.dev: https://pkg.go.dev/github.com/koss-null/funcfrog
• goreportcard.com: https://goreportcard.com/report/github.com/koss-null/funcfrog
• coverage service link (codecov, coveralls, etc.):
  the coverage bage is generated manually, but there is a mandatory pipeline that generates it
  https://github.com/koss-null/FuncFrog/actions/runs/17119494898/job/48557009689

Pull Request content

• The package has been added to the list in alphabetical order.
• The package has an appropriate description with correct grammar.
• As far as I know, the package has not been listed here before.

Category quality

Note that new categories can be added only when there are 3 packages or more.

Packages added a long time ago might not meet the current guidelines anymore. It would be very helpful if you could check 3-5 packages above and below your submission to ensure that they also still meet the Quality Standards.

Please delete one of the following lines:

• The packages around my addition still meet the Quality Standards.

Thanks for your PR, you're awesome! 😎

Summary by CodeRabbit

• Documentation
  • Added a new Functional entry: FuncFrog — a Go 1.18+ library of functional helpers (Map, Filter, Reduce, and stream operations) featuring lazy evaluation, error handling, safe type conversion, and low-allocation, performance-oriented implementations to improve discoverability of modern generics-based utilities for Go.

[coderabbitai]

Walkthrough

Added a new Functional entry to README: "FuncFrog", a Go 1.18+ functional helpers library providing Map, Filter, Reduce and other generic slice stream operations with lazy evaluation, error handling, safe conversions, and low-allocation implementations.

Changes

Cohort / File(s)	Summary
Docs README.md	Added a Functional section entry for FuncFrog describing features: Go 1.18+ support, generic slice operations (Map, Filter, Reduce), lazy evaluation, error handling, safe type conversion, and low-allocation implementations.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I twitch my nose at README’s light,
A frog hops in with functions bright.
Map and Filter, Reduce in play,
Lazy leaps and errors kept at bay.
Low-alloc hops—docs cheer the night. 🐇🐸

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 5ae506d and c1f0768.

📒 Files selected for processing (1)

• README.md (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• README.md

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Codacy Static Code Analysis

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Thank you for contributing to awesome-go. We will review your contribution as soon as possible.

Make sure you add the links in the body of the pull request that are requested in the contribution guide:

• repo link
• pkg.go.dev
• goreportcard.com
• coverage

Your project is under review. It may take a few days to be approved.

[koss-null]

Feel free to contact me as the maintainer of the project by any questions

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

README.md (1)

1217-1217: Polish description casing and tighten copy to match Awesome-Go style.

• Start the blurb with a capitalized word (avoid leading "a ...").
• Prefer concise, neutral phrasing and avoid marketing-y wording like "performance-focused".
• Keep a single, short sentence; many entries use parentheses for examples.

Alphabetical placement under Functional looks correct (between “fuego” and “go-functional”), but please double-check with the repo’s sort/CI script.

Apply this diff to improve style and brevity:

- - [FuncFrog](https://github.com/koss-null/FuncFrog) - a Go 1.18+ functional helpers library providing Map, Filter, Reduce and other stream operations on generic slices with lazy evaluation, safe type conversion, and performance-focused, low-allocation implementations.
+ - [FuncFrog](https://github.com/koss-null/FuncFrog) - Go 1.18+ functional helpers for generic slices (Map, Filter, Reduce) with lazy evaluation, safe type conversion, and low allocations.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between e4167bb and 5ae506d.

📒 Files selected for processing (1)

• README.md (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Codacy Static Code Analysis

[koss-null]

Changed the description according to the bot's advice

[avelino]

Thank you for your contribution! The PR is well-prepared and checks are passing. However, there's one issue that needs to be addressed:

Missing pkg.go.dev Badge:
The repository README is missing the pkg.go.dev badge. While you have a text link to pkg.go.dev, the quality standards require a badge/shield in the README badges section similar to the Go Report Card and License badges you already have.

Please add a pkg.go.dev badge to your repository README. You can use:

[![Go Reference](https://pkg.go.dev/badge/github.com/koss-null/funcfrog.svg)](https://pkg.go.dev/github.com/koss-null/funcfrog)

Note: This is the same issue as PR #5783. Once you add the badge to both repositories, I'll approve both PRs.