-
Notifications
You must be signed in to change notification settings - Fork 15
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
Future incompatibility warning because of steamy-vdf's dependency on nom 1.2.4 #19
Comments
Thanks for the notice! Something that would be extremely helpful would be more testing with #9. Just seeing if there are any parsing/deserialization issues on any manifests is the big one |
FWIW, I'm now using the |
There will be significant changes before the actual v2 release for Leaving this issue open for visibility |
I don't think there's anything to change here, but just figured I'd mention it in case anyone else runs into it. I tried integrating 2.0.0-alpha.0, and Windows Defender complained about there being a trojan. However, I wasn't able to reproduce it after rebuilding, and Virus Total didn't find any issues, so ¯\_(ツ)_/¯ Otherwise, it's working fine. |
Rust is pretty good at getting false positives from anti-viruses because one of its initial popular uses was in malware. Mostly because static-linking makes portable executables and cross compiling a lot easier (Go is also popular here for the same reason) |
steamlocate requires steamy-vdf which requires a in the future unsupported version of nom (1.2.4). This should get fixed with a future release of steamlocate WilliamVenner/steamlocate-rs#19
|
I opened a ticket for steamy-vdf, but since it doesn't seem to be maintained, I thought it was worth raising here as well for awareness.
Using Rust 1.68.0, this warning is displayed while building:
The text was updated successfully, but these errors were encountered: