<div dir="auto">Let's all please take a time out from the naming discussion.</div><div class="gmail_extra"><br><div class="gmail_quote">On Sep 14, 2017 11:15 AM, "Stefan Krah" <<a href="mailto:stefan@bytereef.org">stefan@bytereef.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Thu, Sep 14, 2017 at 11:06:15AM -0700, Mike Miller wrote:<br>
> On 2017-09-14 10:45, Stefan Krah wrote:<br>
> >I'd expect something like a C struct or an ML record.<br>
><br>
> Struct is taken, and your second example is record.<br>
<br>
*If* the name were collections.record, I'd expect collections.record to<br>
be something like a C struct or an ML record. I'm NOT proposing "record".<br>
<br>
<br>
> > from dataclass import dataclass<br>
> ><br>
> >This is more intuitive, since the PEP example also has attached methods<br>
> >like total_cost(). I don't think this is really common for records.<br>
><br>
> Every class can be extended, does that mean they can't be given appropriate names?<br>
<br>
A class is not a record. This brief conversation already convinced me that<br>
"record" is a bad name for the proposed construct.<br>
<br>
<br>
<br>
Stefan Krah<br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
Python-Dev mailing list<br>
<a href="mailto:Python-Dev@python.org">Python-Dev@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/python-dev" rel="noreferrer" target="_blank">https://mail.python.org/<wbr>mailman/listinfo/python-dev</a><br>
Unsubscribe: <a href="https://mail.python.org/mailman/options/python-dev/guido%40python.org" rel="noreferrer" target="_blank">https://mail.python.org/<wbr>mailman/options/python-dev/<wbr>guido%40python.org</a><br>
</blockquote></div></div>