I'm not arguing this is a good thing. But I am saying that for the vast majority of programmers out there they use that pattern as a way of determining if they have those three attributes. It's cargo cult programming in a sense but it's also the only signal they've ever known.
I think calling Rust that would confuse people more than anything. They will look for their traditional inheritance style relationships and be frustrated that there is not really any support for it. Better to teach the features that Rust actually has, than to try and fit some uber generic definition of "Objects" that's not going to serve newcommers.
Re:Announcing Rust 1.20
by imtringued on Friday September 01, 2017 @05:20AM
(#15147129)
Code organisation. Classes are basically used as datatype specific namespaces.
In Haskell you have to deal with the possibility of record types sharing the same field names.
But why? That's such a weird thing to look for. Clearly there's a reason they think they want "objects", but what is it? And why the focus on what syntax these objects have?