Contribution
Are you considering contributing to this project? That’s great; help is always welcome — and contributing is about much more than writing code.
Reporting a bug
Section titled “Reporting a bug”Found something that looks like a bug? Open a bug report. The template will ask for everything needed to reproduce and diagnose it — the more of those fields you can fill in concretely, the faster a fix can land.
Suggesting an idea
Section titled “Suggesting an idea”For concrete feature requests, API changes, or behavior tweaks, open a feature request. The template asks you to describe the problem, the solution you’d like, and alternatives you’ve considered.
If you’re not sure yet whether your idea fits — or you just want to think out loud about a use case — a discussion is the better starting point. FastCSV deliberately stays small, fast, and dependency-free, so many reasonable-sounding features turn out to be out of scope.
Improving the documentation
Section titled “Improving the documentation”Documentation issues — unclear wording, missing examples, broken links, outdated information — are very welcome. Open a documentation issue describing what you’d like to see changed and where.
Helping other users
Section titled “Helping other users”Answering questions in discussions is one of the most valuable ways to contribute. If you’ve solved a tricky problem with FastCSV, sharing how you did it helps the next person who hits the same wall.
Sharing how you use FastCSV
Section titled “Sharing how you use FastCSV”If FastCSV is part of something you’ve built — an open-source project, a blog post, a benchmark, a talk — I’d love to hear about it in the discussions. Real-world usage shapes the project’s direction.
Spreading the word
Section titled “Spreading the word”Starring the repository, recommending FastCSV where it fits, or mentioning it to a colleague who’s wrestling with CSV all help the project stay healthy.