Git Product home page Git Product logo

abomonation_derive's People

Contributors

benesch avatar d-e-s-o avatar dtolnay avatar frankmcsherry avatar milibopp avatar mystor avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

abomonation_derive's Issues

Derivations for recursive types

It seems like the derivation rules head out into crazy-land when we have type that may contain themselves, like

#[derive(Abomonation)]
struct TreeNode<D> {
    data: D,
    children: Vec<TreeNode<D>>,
}

When one attempts to use such a type with the T: Abomonation constraint, Rust complains thusly:

error[E0275]: overflow evaluating the requirement `TreeNode<i32>: abomonation::Abomonation`                                                                                          
  --> examples/types.rs:33:5                                                                                                                                                         
   |                                                                                                                                                                                 
33 |     test(&TreeNode::new(0));                                                                                                                                                    
   |     ^^^^                                                                                                                                                                        
   |                                                                                                                                                                                 
   = note: required because of the requirements on the impl of `abomonation::Abomonation` for `std::vec::Vec<TreeNode<i32>>`                                                         
   = note: required because of the requirements on the impl of `abomonation::Abomonation` for `TreeNode<i32>`                                                                        

This doesn't seem to be a problem for serde, whose Serialize and Deserialize traits derive correctly enough to allow Rust to make progress. The unsafe_abomonate! macro produces implementations, but doesn't work with generic parameters.

Is this something that is expected to work, or perhaps annoying and non-trivial using syn, or .. any input you have would be great!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.