-
Notifications
You must be signed in to change notification settings - Fork 3.3k
simplification of Rust bridge implementations #4605
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Currently, the Rust bridge dynamic_hash is not compiled in, so this needs to be verified manually.
| edition = "2024" | ||
|
|
||
| [dependencies] | ||
| anyhow = "1.0.100" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd avoid third-party crates in dependencies.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The goal of this PR is to simplify the code, and avoid having to implement a custom error enum for (currently) one situation.
Why should third-party crates be avoided? A big advantage of Rust is its crate ecosystem. All bridges that currently exist depend on many third-party crates anyways.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding a dependency just to create an error that will be ignored anyway? Looks very much like bloat.
These changes move duplicate code from the crates
generic_hashanddynamic_hashinto thehashcat-syscrate, allowing its reuse in both bridges (and all future ones).Additionally, the structure of
hashcat-syswas slightly modified to allow new Rust bridges to be implemented more easily.Various other minor changes and small doc updates were made.