Hi Erick,
Thanks for the heads-up. I should've be more specific on the title. Yes,
I'm only after the offending wrapper function.
-Ed
On Sat, Mar 22, 2014 at 10:54 PM, Erick Tryzelaar erick.tryzel...@gmail.com
wrote:
Hello Edward,
I'm not sure how to help with this variance bug, but I
Whoops, excluded the mailing list.
On 22 March 2014 11:53, Edward Wang edward.yu.w...@gmail.com wrote:
`to_encode_object` has type `EncodableEncoder'a` so
`to_encode_object.encode(...)`
requires an Encoder instance with lifetime 'a, the one defined in the
struct bound.
The problem I
This sounds similar to the issues I had when trying to use
extra::serialize::Encoder and Encodable - as it's set up now, I can't have
a method take a a parameter defined to be Encodable and use my choice of
Encoder to stringify it. One suggestion made was to implement Encoder for
~Encoder, but
I was thinking something mimicking the new Hash/Hasher design. They are
actually very similar to each other, aren't they? Too big the change?
-Ed
On Sun, Mar 23, 2014 at 12:53 AM, Neil LoBracco niceguyn...@gmail.comwrote:
This sounds similar to the issues I had when trying to use
Comex,
I think it would. And it's also quite close to my Hash/Hasher analogy. The
only problem seems to be that the scope will be too big.
-Ed
On Sun, Mar 23, 2014 at 1:43 AM, comex com...@gmail.com wrote:
On Sat, Mar 22, 2014 at 10:24 AM, Edward Wang edward.yu.w...@gmail.com
wrote:
But
On Sat, Mar 22, 2014 at 2:35 PM, Sean McArthur s...@seanmonstar.com wrote:
How is it different from having the generic on the trait itself?
Because then a single object of type T:Encodable can be used with any
encoder, without needing to be instantiated for the type of encoder at
the
Hello!,
I'm learning rust and finding myself fighting the language a little and so
I could do with a bit of help.
In my code completion project I have a function which parses 'use' view
items (using libsyntax) and currently returns a vector of vectors of
strings representing fully qualified
