<div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial"><div><br>> To me, 'pop' implies mutation. Tuples do not have a pop method, and it
</div><div>> is not obvious to me that either tuples or frozensets should. What are
> the use cases that are not better served by converting to list or set?
<br>> -- <br>
> Terry Jan Reedy<br><br><br>1) coverting to set or list is O(n) in time<br>2) if I have to keep the old copy,<br> standard set solution will be O(n) both in time and space!<br><br>working examples:<br> 1) priority queue:<br> insert and pop occur<br> 2) share immutable data to difference subroutines:<br> each one can modify local copy safely and concurrency.<br><br><span id="transmark" style="display: none; width: 0px; height: 0px;"></span><br><br><br>
</div></div><br><br><span title="neteasefooter"><p> </p></span>