I come from the Java world so please excuse me as a complete Rust noob. In my OO-stuff, there are common methods as well as object-type-specific ditto. I have in this example showed how I wanted to do this in Rust but failed. trait Speak { fn speak(&self) -> String; } enum Animal { Dog(D…

I believe I should try-out @mroth 's solution before I take any further step. With respect to OOP, my existing implementations support a base-class that offer a (virtual) encode() method. This class is then extended by object-specific (int, string, array, etc.) classes having object-specific method…

Speaking about @mroth I guess you mean cbor-core? CBOR - Wikipedia - what I am seeing it another binary serialization format, looks like you trying to understand how OOP works in rust. Rust is not classic OOP language like Java and C++. You can do certain OOP things, but Rust never targeted to be …

Thanx! I hope this thread can be of some use for other people having another background and would like to (in some way) emulate OOP. One comment: if Dog has a whole bunch of specific methods, the match approach seems a bit awkward. I would consider a get_dog() method giving a handle to the dog ob…

I released cbor-core@0.5.1 / CHANGELOG : The most notable updates are optional support for crates such as serde, chrono, time, and several big-integer crates. Another important improvement is the addition of mitigations against malicious inputs. Functionally, I think it is getting close to feature-…

Yes, I agree. If Dog has many type-specific methods, writing explicit match delegation for every method becomes cumbersome. I tried another approach, which was already hinted at in one of the comments: impl Animal { fn get_speak(&self) -> &dyn Speak { match self { Self::Dog…

This will be my final post about CBOR::Core in this thread. Michael, you have done an amazing job and in a very short time. The code looks very neat as well. I will start trying out features while (slowly...) becoming a bit more "Rusty".

I’ve found one interesting macro-crate, for a task you’ve described, it can reduce a lot of boilerplate code: use enum_dispatch::enum_dispatch; #[enum_dispatch] trait MyTrait { fn do_some(&self); } struct A1; struct A2; impl MyTrait for A1 { fn do_some(&self) { println!("A1"); …

Thanks! It sure looks pretty. What I don't get is how this code could handle data (fields) associated with A1 and A2 that may be entirely different. For a solution to be comparable to what I have done in Java, JavaScript, and Python objects also need to be accessible in a shared mode. As a proo…

Hi @cyberphone , Here is a complete example of how static polymorphism with field access can work in Rust, using macros, with no more code than your dyn Trait example. As you can see, there is almost no enum boilerplate here. I implement the trait for normal structs as usual, and then use enum_disp…

Basic Object Oriented Programming in Rust

help

mroth April 14, 2026, 12:35am 108

This will be my final post about CBOR::Core in this thread. A new release is available:

Cbor-core 0.6.0: A deterministic CBOR::Core encoder/decoder

Topic		Replies	Views
Could enums be considered an anti-pattern?	13	9497	January 12, 2023
Suggestion for making Rust's trait system more usable for generics community	75	4892	April 13, 2020
What does "Rust & OOP" mean to you? help	35	14161	July 3, 2022
Noob question again: enum and struct?	48	12444	June 17, 2024
State & future of dynamic polymorphism and OOP	18	1155	June 13, 2025

Basic Object Oriented Programming in Rust

Related topics