Michael Lamparski

N.B. why I care so much: Just earlier today, working on a diophantine equation solver, I *almost* wrote the following: ```rust trait SqrtExt { /// Compute the (exact) square root,...

* Continued fractions (including the function to obtain one from the square root of a rational) are probably best implemented in another crate. * I am sympathetic to the `&Self...

Supporting `#[derive(Snafu)]` on structs is also useful for reasons beyond this use case. For error types that wrap errors from FFI, many C APIs just give integer error codes, or...

Hmm? You mean, a reason for the existing feature in yamlcpp that supports `\_` escapes? Without knowing much about the project, I would assume this is because yamlcpp describes itself...

Worth noting: in the examples in the YAML 1.1 spec, it is suggested that `\_` is equivalent to `\xA0`. This is correct, but they mean `\xA0` *in YAML* (not in...

Older report: https://github.com/intellij-rust/intellij-rust/issues/2234 Yeah, this constantly annoys me.

Idk this is the author of [effing-mad](https://github.com/rosefromthedead/effing-mad) so if they have a use case, I believe them 🤣

Hmmm. This is a tough one. @lloydmeta, would it be correct to say that "no usage of `unsafe`" is one of the design goals of Frunk? I've always seen frunk...

Interesting. Yeah an effect system library definitely sounds like the kind of thing that needs this. Funny, though, I would've expected them to require some concept of "minimal common superset"...

> Type comparison is easy via the specialization feature, which is unfortunately currently unsound. I think this use case would be sound as it doesn't involve lifetimes but who knows....