Skip to content

chore: enforce more rigorous code with clippy #34

Open
@jeertmans

Description

@jeertmans

What

Currently, only a few clippy rules are used, see:

#![deny(missing_docs)]
#![deny(missing_debug_implementations)]
#![warn(clippy::must_use_candidate)]
#![allow(clippy::doc_markdown, clippy::module_name_repetitions)]
#![cfg_attr(docsrs, feature(doc_auto_cfg))]
#![doc = include_str!("../../README.md")]

I'd like to enforce a more uniform code style by adding other clippy rules, such as clippy::pendatic.

How to

It's a very open issue, and I would love to get suggestion from the community, on some clippy rules that I could use.
Of course, using some new rules might need to edit the current code base.

Metadata

Metadata

Assignees

No one assigned

    Labels

    good first issueGood for newcomershacktoberfestIssue that is created for the Hacktoberfest eventlintingLinting files to match some guidelines

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions