From: Konstantin Osipov <kostja@tarantool.org> To: tarantool-patches@freelists.org Cc: vdavydov.dev@gmail.com, Kirill Shcherbatov <kshcherbatov@tarantool.org> Subject: Re: [tarantool-patches] [PATCH v3 4/4] box: introduce functional indexes in memtx Date: Thu, 18 Jul 2019 12:54:22 +0300 [thread overview] Message-ID: <20190718095422.GE21191@atlas> (raw) In-Reply-To: <d795cfdddfa27dd7f7fe45d684ec84be8f7f87df.1563326037.git.kshcherbatov@tarantool.org> * Kirill Shcherbatov <kshcherbatov@tarantool.org> [19/07/17 09:39]: > +++ b/src/box/CMakeLists.txt > @@ -51,8 +51,9 @@ add_library(tuple STATIC > coll_id_cache.c > field_def.c > opt_def.c > + functional_extractor.c since we started to use func_ and not function_ and functional_ as an abbreviation, let's be consistent and use it everywere, so func_extractor. extractor is not a good name either (and most likely not a good division of responsibilities), but I'll get to it later. > + functional_key.c func_key when a patch adds new modules the commit comment should contain an explanation about what these modules do and why they were added. > index 1dbfe6b26..fdf38598e 100644 > --- a/src/box/alter.cc > +++ b/src/box/alter.cc > @@ -30,6 +30,7 @@ > */ > #include "alter.h" > #include "assoc.h" > +#include "box.h" Kirill, please stop bloating header file dependencies, especially circular ones. If you need to include a dependency like this, you haven't dealt with technical debt. There should be a separate patch which improves modules structure so that this dependency is avoided. The dependency issue is described in the SOP, so I should not have to point it out time and again. -- Konstantin Osipov, Moscow, Russia
next prev parent reply other threads:[~2019-07-18 9:54 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-07-17 1:20 [PATCH v3 0/4] box: functional indexes Kirill Shcherbatov 2019-07-17 1:20 ` [PATCH v3 1/4] box: introduce key_def->is_multikey flag Kirill Shcherbatov 2019-07-17 14:34 ` Konstantin Osipov 2019-07-18 11:20 ` [tarantool-patches] " Kirill Yukhin 2019-07-17 1:20 ` [PATCH v3 2/4] box: refactor key_validate_parts to return key_end Kirill Shcherbatov 2019-07-18 9:41 ` Konstantin Osipov 2019-07-18 11:21 ` [tarantool-patches] " Kirill Yukhin 2019-07-17 1:20 ` [PATCH v3 3/4] box: introduce tuple_extra infrastructure Kirill Shcherbatov 2019-07-18 9:47 ` Konstantin Osipov 2019-07-17 1:20 ` [PATCH v3 4/4] box: introduce functional indexes in memtx Kirill Shcherbatov 2019-07-18 9:50 ` [tarantool-patches] " Konstantin Osipov 2019-07-18 9:54 ` Konstantin Osipov [this message] 2019-07-18 9:55 ` Konstantin Osipov 2019-07-18 10:02 ` Konstantin Osipov 2019-07-22 14:45 ` Vladimir Davydov
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=20190718095422.GE21191@atlas \ --to=kostja@tarantool.org \ --cc=kshcherbatov@tarantool.org \ --cc=tarantool-patches@freelists.org \ --cc=vdavydov.dev@gmail.com \ --subject='Re: [tarantool-patches] [PATCH v3 4/4] box: introduce functional indexes in memtx' \ /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