Description
I'm submitting a feature request
So with a 1.0.0 release in the foreseeable future, it seems like a reasonable course of action to address any missing features, code-structure issues, or subtle bugs before that is released. Thankfully, many of these problems have been annotated with TODO.
I suggest that we enable this cargo fmt lint (temporarily as it is a nightly only feature, and it may be removed in the future) and have someone go through the project and create issues for all outstanding TODOs and annotate them with their respective issue numbers.
There aren't too many of them, between 8 and 10 actionable instances in the project, of which about 4 are probably easily resolvable.
Description
I'm submitting a feature request
So with a 1.0.0 release in the foreseeable future, it seems like a reasonable course of action to address any missing features, code-structure issues, or subtle bugs before that is released. Thankfully, many of these problems have been annotated with
TODO.I suggest that we enable this cargo fmt lint (temporarily as it is a nightly only feature, and it may be removed in the future) and have someone go through the project and create issues for all outstanding TODOs and annotate them with their respective issue numbers.
There aren't too many of them, between 8 and 10 actionable instances in the project, of which about 4 are probably easily resolvable.