Tony Przygienda commented on THRIFT-2945:

OK, rephrased in other points what I read

a) we agree the trait is called serializable then 
b) I will check the README and extend it with namespace example and make sure 
everything conforms. I will add a simple example of custom trait (this default 
c) will look @ the service inheritance test
d) We add Hash. Having said that: I discourage you from moving bask to HashSet. 
BTreeSet/Map can we range-walked which can be a very serious asset. 
e) I will look @ the format issue & fix `rust_safe_case`
f) Understood your reasoning about the Rc<RefCell<Box<.. requirements and no, 
can't tell you anything better.Yes, you pay Rust for the glorious fact that you 
get thread-safe and memory safe compiled code and those semantics express this 
exactly.  The performance is normally pretty decent, I find that cleanly 
written Rust with some optimization @ the end (look for clones ;-) runs faster 
than C++11 I normally write which is quite something but vtables in C++ and 
templates can become performance suckers quickly and the right hand moves are 
so complex to remember/understand that I end up copying tons stuff because 
trying to debug memory on complex C++11 is suicidal.  What I did here in Rust I 
built a Cursor transport underneath and I serialize once & then just rewind and 
read the transport over and over again. De-serialization I need to construct 
the input protocol per incoming snippet since I want to pass those around (i.e. 
have multiple snippets in flight). 

That's a plan ?

> Implement support for Rust language
> -----------------------------------
>                 Key: THRIFT-2945
>                 URL: https://issues.apache.org/jira/browse/THRIFT-2945
>             Project: Thrift
>          Issue Type: New Feature
>          Components: Rust - Compiler, Rust - Library
>            Reporter: Maksim Golov
>            Assignee: Allen George
>             Fix For: 0.11.0
> Work on implementing support for Rust is in progress: 
> https://github.com/maximg/thrift by Simon GĂ©nier and myself.
> It will probably take quite some time to complete. Please keep us updated if 
> there are changes related to our work.

This message was sent by Atlassian JIRA

Reply via email to