-
Notifications
You must be signed in to change notification settings - Fork 13k
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
rusti: Cannot print not-implicitly-copyable variables #7692
Comments
workaround for this issue.
|
I was thinking about this awhile back. I think that the best way to go about doing this would be to just don't re-serialize moved variables. Basically after the user-input code is executed, detect if any of the local bound variables were moved, and don't reserialize them. The bad part is that you can move out of a variable and then use it in a later statement, but this is purely a debugging repl so I don't think that it's too bad. |
…giraffate Demote float_cmp to pedantic See this issue: rust-lang/rust-clippy#7666 This is one of the most frequently suppressed lints. It is deny-by-default. It is not actually clearly wrong, as there are many instances where direct float comparison is actually desirable. It is only after operating on floats that they may lose precision, and that depends greatly on the operation. As most correctness lints have a much higher standard of error, being based on hard and fast binary logic, this should not be amongst them. A linter is not a substitute for observing the math carefully and running tests, and doing the desirable thing is even more likely to lead one to want exact comparisons. changelog: Demote [`float_cmp`] from correctness to pedantic lints
I think
rusti
should prints the value ofv
.The text was updated successfully, but these errors were encountered: