Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #102646 > unrolled thread

Re: Heap Implementation

Started bysrinivas devaki <mr.eightnoteight@gmail.com>
First post2016-02-08 08:45 +0530
Last post2016-02-08 08:45 +0530
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Heap Implementation srinivas devaki <mr.eightnoteight@gmail.com> - 2016-02-08 08:45 +0530

#102646 — Re: Heap Implementation

Fromsrinivas devaki <mr.eightnoteight@gmail.com>
Date2016-02-08 08:45 +0530
SubjectRe: Heap Implementation
Message-ID<mailman.85.1454901359.2317.python-list@python.org>
On Feb 8, 2016 7:07 AM, "Cem Karan" <cfkaran2@gmail.com> wrote:
>
>
>
> I know that there are methods of handling this from the client-side
(tuples with unique counters come to mind), but if your library can handle
it directly, then that could be useful to others as well.

yeah it is a good idea to do at client side.
but if it should be introduced as feature into the library, instead of
tuples, we should just piggyback a single counter it to the self._indexes
dict, or better make another self._counts dict which will be light and fast.
and if you think again with this method you can easily subclass with just
using self._counts dict  in your subclass. but still I think it is good to
introduce it as a feature in the library.

Regards
Srinivas Devaki
Junior (3rd yr) student at Indian School of Mines,(IIT Dhanbad)
Computer Science and Engineering Department
ph: +91 9491 383 249
telegram_id: @eightnoteight

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web