From: Nikita Pettik <korablev@tarantool.org> To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH 5/7] box/error: clarify purpose of reference counting in struct error Date: Wed, 25 Mar 2020 01:40:10 +0000 [thread overview] Message-ID: <20200325014010.GD30598@tarantool.org> (raw) In-Reply-To: <33767c0b-2bb6-8bf3-87a5-d3b1994f05d0@tarantool.org> On 23 Feb 18:43, Vladislav Shpilevoy wrote: > Thanks for the patch! > > How about merging this commit into the previous one? > > On 19/02/2020 15:16, Nikita Pettik wrote: > > --- > > src/lib/core/diag.h | 9 +++++++++ > > 1 file changed, 9 insertions(+) > > > > diff --git a/src/lib/core/diag.h b/src/lib/core/diag.h > > index 5271733cb..a9181c522 100644 > > --- a/src/lib/core/diag.h > > +++ b/src/lib/core/diag.h > > @@ -72,6 +72,15 @@ struct error { > > error_f raise; > > error_f log; > > const struct type_info *type; > > + /** > > + * Reference counting is basically required since > > + * instances of this structure are available in Lua > > + * as well (as cdata with overloaded fields and methods > > + * by the means of introspection). Thus, it may turn > > + * out that Lua's GC attempts at releasing object > > + * meanwhile it is still used in C internals or vice > > + * versa. For details see luaT_pusherror(). > > Hmm, no, it can't anymore. Now it can't. But it used to, until ref in luaT_pusherror() was introduced. So may comment refer to that quite ancient fix (I just wondered why can't we get rid of ref counter and came up with this explanation). > Lua can't delete an error object, > if it is still used in C. This looks like an artifact from the > previous patch version, were you unreferenced all errors when > diag was cleared. > > > + */ > > int refs; > > /** > > * Errno at the moment of the error > >
next prev parent reply other threads:[~2020-03-25 1:40 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-02-19 14:16 [Tarantool-patches] [PATCH 0/7] Stacked diagnostics area Nikita Pettik 2020-02-19 14:16 ` [Tarantool-patches] [PATCH 1/7] box: rename diag_add_error to diag_set_error Nikita Pettik 2020-02-19 14:16 ` [Tarantool-patches] [PATCH 2/7] box/error: introduce box.error.set() method Nikita Pettik 2020-02-19 14:26 ` Cyrill Gorcunov 2020-02-19 14:30 ` Nikita Pettik 2020-02-19 14:53 ` Cyrill Gorcunov 2020-02-19 14:16 ` [Tarantool-patches] [PATCH 3/7] box/error: don't set error created via box.error.new to diag Nikita Pettik 2020-02-22 17:18 ` Vladislav Shpilevoy 2020-03-25 1:02 ` Nikita Pettik 2020-03-26 0:22 ` Vladislav Shpilevoy 2020-03-26 1:03 ` Nikita Pettik 2020-02-19 14:16 ` [Tarantool-patches] [PATCH 4/7] box: introduce stacked diagnostic area Nikita Pettik 2020-02-19 21:10 ` Vladislav Shpilevoy 2020-02-20 11:53 ` Nikita Pettik 2020-02-20 18:29 ` Nikita Pettik 2020-02-23 17:43 ` Vladislav Shpilevoy 2020-03-25 1:34 ` Nikita Pettik 2020-02-19 14:16 ` [Tarantool-patches] [PATCH 5/7] box/error: clarify purpose of reference counting in struct error Nikita Pettik 2020-02-23 17:43 ` Vladislav Shpilevoy 2020-03-25 1:40 ` Nikita Pettik [this message] 2020-02-19 14:16 ` [Tarantool-patches] [PATCH 6/7] iproto: refactor error encoding with mpstream Nikita Pettik 2020-02-23 17:44 ` Vladislav Shpilevoy 2020-03-25 1:42 ` Nikita Pettik 2020-02-19 14:16 ` [Tarantool-patches] [PATCH 7/7] iproto: support error stacked diagnostic area Nikita Pettik 2020-02-23 17:43 ` Vladislav Shpilevoy 2020-03-25 1:38 ` Nikita Pettik 2020-02-22 17:18 ` [Tarantool-patches] [PATCH 0/7] Stacked diagnostics area 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=20200325014010.GD30598@tarantool.org \ --to=korablev@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 5/7] box/error: clarify purpose of reference counting in struct error' \ /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