RetroSearch Browse

Mon Aug 29 18:51:12 EDT 2016 · https://mail.python.org/pipermail/python-dev/2016-August/145937.html

Anyway, given the outcome of Dino's tests I have no objections to the
PEP. (Though using Christian's hack would be cool.)

On Mon, Aug 29, 2016 at 3:28 PM, Christian Heimes <christian at python.org> wrote:
> On 2016-08-29 23:38, Brett Cannon wrote:
>> That means we still want to find a solution to attach arbitrary data to
>> code objects without sacrificing performance. One proposal is what's in
>> PEP 523 for the extra field. Another option is to make the memory
>> allocator for code objects pluggable and introduce a new flag that
>> signals that the object was created using a non-default allocator.
>> Obviously we prefer the former solution due to its simplicity. :)
>
> May I remind you that you can have the field with no extra memory cost?
> :) The struct has sub-par alignments.
>
> Christian
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: https://mail.python.org/mailman/options/python-dev/guido%40python.org

-- 
--Guido van Rossum (python.org/~guido)

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2016-August/145937.html below:

[Python-Dev] Update on PEP 523 and adding a co_extra field to code objects