Merge branch 'main' into rust

Author: kelvins

.github/pull_request_template.md

@@ -0,0 +1,10 @@
+Before opening a Pull Request, please read the following items:
+1. Make sure you have read the [CONTRIBUTING](../CONTRIBUTING.md) guidelines
+2. Make sure no other PR is implementing the same change
+3. Make sure the Continuous Integration workflows (Github Actions) are all passing
+4. If in doubt about how to approach another contributor, read our [CODE OF CONDUCT](../CODE_OF_CONDUCT.md) guidelines
+
+<!-- Remove the above section before opening the pull request -->
+
+# Description
+<!-- Add a brief description of the changes related to this Pull Request -->

.gitignore

@@ -1 +1,2 @@
 .metals
+__pycache__/

CODE_OF_CONDUCT.md

@@ -0,0 +1,79 @@
+
+# Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

CONTRIBUTING-pt-br.md

@@ -1,22 +1,58 @@
-[![en](https://img.shields.io/badge/lang-en-red.svg)](CONTRIBUTING.md)
-[![pt-br](https://img.shields.io/badge/lang-pt--br-green.svg)](CONTRIBUTING-pt-br.md)
 # Contributing
 
-You can contribute in 3 ways: creating issues, opening pull requests, and reviewing pull requests.
-## Creating Issues
+Thanks for your interest in contributing! We appreciate your support, and we welcome contributions from the community.
 
-Feel free to create an issue if you encounter any problems, have any suggestions, or would like a specific new algorithm or language to be included. Open a new PR directly in cases of minor corrections or inclusion of algorithms already listed in a language not yet implemented.
+Before you start contributing, please take a moment to review this document to understand the process and guidelines for contributing to our project.
 
-Before creating the issue, check for similar issues and remember to detail the problem encountered or proposed suggestion.
+## Code of Conduct
 
-## Opening Pull Requests
+We have adopted a [Code of Conduct](./CODE_OF_CONDUCT.md) that we expect all community members to follow. Please make sure to review and adhere to it in all interactions within our community.
 
-It is also possible to contribute by opening a Pull Request (PR) with a solution to a problem or including a new algorithm.
+## How Can I Contribute?
 
-When opening a PR, remember to include a relevant description of the changes made and add a link in the project's README if new algorithms are incorporated.
+There are various ways to contribute:
 
-## Reviewing Pull Requests
+- Reporting Issues: If you encounter a bug or have a feature request, please open an issue on GitHub.
+- Code Contributions: If you are a developer, you can help us by submitting pull requests.
+- Documentation: Improvements to our documentation are always welcome.
 
-Another way to contribute to the project is by reviewing open PRs. If you have mastery of an algorithm, data structure, or even a specific programming language, feel free to help review the open PRs.
+## Reporting Issues
 
-When reviewing, remember to be cordial/polite and, if possible, manually test the change or correction before approving the PR.
+If you encounter an issue or have a feature request, please follow these steps:
+
+1. Check if the issue or feature request already exists.
+2. If it doesn't exist, please open a new issue, providing a clear and detailed description of the problem or request.
+3. Use a descriptive title, provide steps to reproduce the issue, and specify your environment.
+
+## Development Guidelines
+
+Before you start working on a contribution, please keep in mind the following guidelines:
+
+- Adhere to our [Code of Conduct](./CODE_OF_CONDUCT.md).
+- Respect and follow existing project coding standards.
+- Write clear and concise commit messages.
+- Test your changes thoroughly.
+- Make your code clean and readable.
+- Document your code as necessary.
+
+## Submitting Pull Requests
+
+To submit a pull request, please follow these steps:
+
+1. Fork the repository.
+2. Create a new branch for your contribution: `git checkout -b feature/my-contribution`.
+3. Make your changes and commit them.
+4. Ensure that your code is properly tested.
+5. Create a pull request against our main branch.
+6. Clearly describe your changes, why they are necessary, and how to test them.
+7. Be responsive to feedback and participate in the review process.
+
+## Review Process
+
+All contributions will be reviewed by project maintainers. We may provide feedback or request additional changes. Your contribution will be merged once it meets our standards.
+
+## Getting Help
+
+If you need assistance or have any questions, you can reach out to us. We are here to help you with your contributions.
+
+We look forward to your contributions and thank you for your time and effort!