![]() This is the best we can do for this without rearchitecting when we rewrite backpassing to plain ol' assignments. In this case, if we see a var and there is no annotation (thus probably not a cast), then it's safe to rewrite to a `let` instead of an `expect`. This way, we don't get a warning that is **unfixable**. We are not trying to solve every little warning edge case with this fix. We simply just can't allow there to be a warning that the user can't make go away through some means. All other edge cases like pattern matching on a single contructor type with expect warnings can be fixed via other means. |
||
---|---|---|
.github | ||
crates | ||
examples | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
CHANGELOG.md | ||
CONTRIBUTING.md | ||
Cargo.lock | ||
Cargo.toml | ||
LICENSE | ||
README.md | ||
flake.lock | ||
flake.nix |
README.md
Installation
How to use
For more information please see the user manual.
Contributing
Want to contribute? See CONTRIBUTING.md to know how.
Note
The name comes from Howard Aiken, an American physicist and a pioneer in computing.