From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: tarantool-patches@freelists.org,
Konstantin Osipov <kostja@tarantool.org>
Cc: vdavydov.dev@gmail.com
Subject: Re: [tarantool-patches] Re: [PATCH 1/3] salad: make heap struct more friendly to use
Date: Fri, 22 Feb 2019 21:38:50 +0300 [thread overview]
Message-ID: <caadccdb-bb77-8134-38ab-109c98778bff@tarantool.org> (raw)
In-Reply-To: <20190222182618.GB1691@chai>
On 22/02/2019 21:26, Konstantin Osipov wrote:
> * Vladislav Shpilevoy <v.shpilevoy@tarantool.org> [19/02/22 14:39]:
>> Now heap API works with struct heap_node only, which forces a
>> user to constantly call container_of. Such a code looks really
>> awful. This commit makes heap taking and returning user defined
>> structures, and removes container_of clue.
>>
>> It is worth noting, that the similar API rb-tree and b-tree
>> have. Even rlist has its rlist_*_entry() wrappers, and mhash
>> provides macroses to define your own value type.
>
> OK to push.
>
>
> --
> Konstantin Osipov, Moscow, Russia, +7 903 626 22 32
> http://tarantool.io - www.twitter.com/kostja_osipov
>
Pushed to 2.1.
next prev parent reply other threads:[~2019-02-22 18:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 11:38 [PATCH 0/3] Make heap API more friendly Vladislav Shpilevoy
2019-02-22 11:38 ` [PATCH 1/3] salad: make heap struct more friendly to use Vladislav Shpilevoy
2019-02-22 18:26 ` [tarantool-patches] " Konstantin Osipov
2019-02-22 18:38 ` Vladislav Shpilevoy [this message]
2019-02-22 11:38 ` [PATCH 2/3] salad: do not touch struct heap_node.pos in user's code Vladislav Shpilevoy
2019-02-25 12:46 ` Vladimir Davydov
2019-02-22 11:39 ` [PATCH 3/3] salad: fix heap reserve() behaviour Vladislav Shpilevoy
2019-02-22 18:31 ` [tarantool-patches] " Konstantin Osipov
2019-02-22 18:38 ` [tarantool-patches] " Vladislav Shpilevoy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=caadccdb-bb77-8134-38ab-109c98778bff@tarantool.org \
--to=v.shpilevoy@tarantool.org \
--cc=kostja@tarantool.org \
--cc=tarantool-patches@freelists.org \
--cc=vdavydov.dev@gmail.com \
--subject='Re: [tarantool-patches] Re: [PATCH 1/3] salad: make heap struct more friendly to use' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox