PlasmaFAIR/fortitude

Avoid (public) mutable module-scope variables

Open

#681 opened on Jun 22, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Rust (33 forks)auto 404
good first issuerule

Repository metrics

Stars
 (207 stars)
PR merge metrics
 (PR metrics pending)

Description

parameters should be okay, but as far as I know everything else should be flagged.

By default, it could flag only public variables, as they could be modified from outside the module, causing a massive headache for testing and debugging. Strict mode could forbid any mutable module variables.

Or perhaps it should be the other way around, flagging any mutable module scope variables by default and allow-private being an option?

For names, I was thinking mutable-module-variable, but I'm not sure if "mutable variable" counts as a redundancy.

Contributor guide

Research direction
Tech stack
Domain
Issue type
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Prerequisites
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.