Contributing
First of all, thank you for considering contributing to Azin! ❤️
Whether you're fixing a bug, improving the documentation, proposing a language feature, or writing code, every contribution helps move the project forward.
Before You Start
If you're planning to contribute, we highly recommend joining our Discord server.
Most design discussions, language proposals, and development planning happen there. It's the best place to ask questions, discuss ideas, or make sure someone else isn't already working on the same thing.
Read the Documentation
Before contributing, take a moment to read the documentation. It may already answer your questions or explain why something is implemented the way it is.
For implementation details, APIs, and the compiler's internal architecture, visit our Doxygen documentation
Keep Pull Requests Focused
Please try to keep each pull request focused on a single feature, fix, or improvement.
Smaller pull requests are easier to review, easier to test, and much more likely to be merged quickly.
Follow the Existing Style
Please follow the existing coding style, project layout, and naming conventions whenever possible.
If you're unsure how something should be written, look at nearby code and stay consistent with it.
Discuss Large Changes First
Planning a new language feature? A major refactor? An architectural change?
Please discuss it with us first, preferably on Discord or in a GitHub Discussion, before investing significant time implementing it.
This helps avoid duplicate work and ensures everyone's heading in the same direction.
Documentation Contributions
Documentation improvements are always welcome.
If you notice missing explanations, outdated examples, typos, or confusing sections, feel free to open a pull request.
Be Respectful
Azin is a community project.
Please be respectful, constructive, and welcoming. We want contributing to be an enjoyable experience for everyone.
Thank You
Thanks again for helping improve Azin.
We're excited to see what you build. 🚀