Open rimutaka opened 3 years ago
why are you using regex to parse rust files?
@Feilkin , I'm trying to keep it simple and generic / language agnostic for now. How would you approach it?
Relates to #8 . The regex approach is a big limitation in solving this.
Limitations
The Rust Muncher should be a bit more detailed and accurate. The initial implementation cut a few corners.
for X in Y {...}
- make this a single construct in keywords as opposed to separatefor
andin
///
and//!
are tracked as docs, but/** ... **/
is not.use
is too hard because it can be nested and multiline. Skipped for now.version
andedition
from [package] section because we can't look only in a certain part of the file. I couldn't construct a regex to exclude those two.Potential sensitive data leakage
Local libs are included in the report. E.g.
stackmuncher_lib = { version = "0.2", path = "../../stm_app/stackmuncher_lib" }
includesstackmuncher_lib
.This probably affects other languages. The problem here is in the parent path. It should be logged as a separate issue.