We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In addition to the "lazy" and "embedded friendly" structs with getters we have now, it would be neat to add a fully parsed representation as well.
I'm imagining something like
struct MessageA { raw: [u8; 8] } struct MessageAParsed { signal_1: u8, signal_2: f64, } impl DecodeCan for MessageA { type Output = MessageAParsed; fn decode(&self) -> Result<Self::Output, CanError> { Ok(MessageAParsed { signal_1: self.signal_1()?, signal_2: self.signal_2()?, }) } } impl EncodeCan for MessageAParsed { type Output = MessageA; fn encode(&self) -> Result<Self::Out, CanError> { … } }
as a first step and the maybe also doing a DecodedMessage enum to go all in.
DecodedMessage
Let me know if you think this is of any use to you in practice :)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
In addition to the "lazy" and "embedded friendly" structs with getters we have now, it would be neat to add a fully parsed representation as well.
I'm imagining something like
as a first step and the maybe also doing a
DecodedMessage
enum to go all in.Let me know if you think this is of any use to you in practice :)
The text was updated successfully, but these errors were encountered: