You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per discussion w/ @nmatsakis , the auto_encode framework should probably make calls to the encoder with fully-qualified type- and enum-names. So, for instance, the "name" field in a Some(13) would not be "Some", but rather core::option::Option (or perhaps ::core::option::Option). A similar alternative would be to pass a path along with the name.
I'm creating this issue for use in a FIXME note in the source.
The text was updated successfully, but these errors were encountered:
This FIXME does not appear to be present, nor does auto_encode exist any more (it now manifests itself as deriving(Encodable)).
I'm not entirely sure that we're even still passing around type names in these. This may be more relevant with repr-type things, but @thestinger changed that recently to print full-qualified type names anyway.
From that, I'm gonna go ahead and close this, if others feel different though, feel free to reopen!
Per discussion w/ @nmatsakis , the auto_encode framework should probably make calls to the encoder with fully-qualified type- and enum-names. So, for instance, the "name" field in a Some(13) would not be "Some", but rather core::option::Option (or perhaps ::core::option::Option). A similar alternative would be to pass a path along with the name.
I'm creating this issue for use in a FIXME note in the source.
The text was updated successfully, but these errors were encountered: