-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Record inheritance #1776
New issue
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
Comments
I think we're pretty firmly wedded to classes without inheritance at this point. Also, keeping our class design the way it is and adding records with inheritance sounds complex to me. Closing, reopen if anybody strongly opposes that. |
struct inheritance, single inheritance... I got the impression some of the rust compiler sourcecode is slightly complicated by its absence, eg situtaions where nodes share the same fields. (spans).. see spanned, then a series of duplicate symbols with _ prefixes like variant_ =spanned etc .. maybe i'm overlooking something Would it create complex interactions eg with generics, inference, impls, traits ? |
…, r=llogiq Don't trigger large_enum_variant in external macros Closes rust-lang#1776 (the potential JSON output issue is not something we can fix in Clippy and I can't reproduce it anymore) changelog: Don't trigger [`large_enum_variant`] in external macros
It would be great to be able to do some thing like this :
type A = { a: int }; type B = {b: int} herit A;
So in fact
B = {a: int, b: int};
It could maybe replace an object model when combined with interfaces.
The text was updated successfully, but these errors were encountered: