llogiq
llogiq
Stupid autocorrect: I meant a *no-op*. Edited my comment.
No, I'm rather thinking about other random stuff, like our custom TyOcc + Hash + Equals implementation. The default type whitelist stuff is likely to be removed anyway when #100...
So `cargo mutagen` should return an error code (instead of success) if at least one mutation survived? Or should we have a threshold?
Under-/overflow issues are the least of my worries: There may be types that implement `AddAssign`, but not `SubAssign` (for example `String`) and the other traits are the same. We may...
This can be done with specialization so we let typeck infer the correct code for us.
I know (and being one of clippy's maintainers I should know :smile:). Another way of doing that is calling `cargo rustc -Z extra-plugins mutagen-plugin`, but that's finicky and relies on...
Of course we can go the `cargo rustc` route, which is easier to set up and don't need to hook into rustc (although I don't recall any breakage w.r.t. the...
Wouldn't that at least require `T: Clone`? Also we already do early return with arguments, so a part of this is already taken care of.
I think I have a solution for this and a few other mutations. Will write something up soon.
See https://llogiq.github.io/2018/03/03/opportune.html