I'd like to suggest - assuming it's not implied - that all aforementioned
PRs should preserve history to date, rather than just having a copy of the
files as they are at present.
Decent walkthrough using a subtree merge -
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
Hey guys,
I'm getting started with Rust, building out a web services framework.
I have an enum methods can return for their response body:
public enum ResponseBody {
Empty,
Text(~str),
JSON(~serialize::Encodable)
}
As you may know, this doesn't work, because Encodable expects a type