Michael Lamparski
Michael Lamparski
This feels to me more like a problem of "how to use Rust," though. (I mean, you *always* have to propagate bounds up in generic functions, and the docs show...
Ahh, I see, it's harder to figure out the right bound from the page of the trait now that rustdoc hides the declaration by default. (N.B. it does currently appear...
p.s. pseudocode for monoid (well, okay, this is more code than pseudo): ```rust pub fn combine_n(&self, mut exp: u64) -> Self { let mut acc = Self::identity(); let mut base...
> However, I still think that we should remove or rename the inherent methods; due to the same names for methods in struct and in trait, compiler could emit some...
That sounds boss.
> If you have some time to try out improvements to `LiftFrom` wrt. using permutations of subsequences that would be super cool =) P.S. my gut feelings on this are...
Something does feel off to me about the asymmetry between `struct HList` and `enum Coproduct` but I can't quite place my finger on it. Aside from that it certainly does...
Ahh, just one thing: If the user wants to query what variant of the enum their Coproduct is, this will be difficult to do since the types of the variants...
Oh, I think I see the issue now. For some SYB trait implementations, `List Coprod!( (), Box )` would result in a trait impl with circular where bounds. How unfortunate...
RE: Variants with matching types: It may be difficult to work with the encoded form *directly,* but I believe there are still use cases for writing generic abstractions (SYB style)....