<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><br class=""><blockquote type="cite" class=""><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">There seem to me to be multiple ways to solve this problem - a newtype(esque) keyword, struct subtyping, or forwarding as Matthew is suggesting</span></div></blockquote></div><div class="">Imho it would make sense to start a topic about inheritance for structs — of cause there a good theories why this isn't possible, but subtyping on its own isn't problematic:</div><div class="">You just have to disallow polymorphism (at least for subtypes with own properties).</div><div class="">I wonder if there has been a decision to just disable inheritance for structs completely to avoid confusion with the lesser strict rules of reference types…</div><div class=""><br class=""></div><div class="">Tino</div></body></html>