From: Alexander Turenko <alexander.turenko@tarantool.org>
To: Oleg Babin <olegrok@tarantool.org>
Cc: Oleg Babin <babinoleg@mail.ru>, tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v3] error: add __concat method to error object
Date: Wed, 15 Jan 2020 14:26:39 +0300 [thread overview]
Message-ID: <20200115112639.4rlwuxssjcshj65c@tkn_work_nb> (raw)
In-Reply-To: <20200110154805.94649-1-olegrok@tarantool.org>
LGTM.
Just two minor comments re commit message.
WBR, Alexander Turenko.
On Fri, Jan 10, 2020 at 06:48:05PM +0300, olegrok@tarantool.org wrote:
> From: Oleg Babin <babinoleg@mail.ru>
>
> Usually functions return pair {nil, err} and expected that err is string.
Curly braces can be interpreted as a table. I would use an apostrophe
instead.
> Let's make the behaviour of error object closer to string
> and define __concat metamethod.
>
> Closes #4489
>
> The case of error "error_mt.__concat(): neither of args is an error"
> is not covered by tests because of #4723
It is better to place all tags below commit message, not in the middle.
The only exception is docbot comment: it should be written after tags.
> ---
> Changes in v3:
> - Improve concatenation logic
> - Add more test cases
> Changes in v2:
> - Added tests
>
> Issue: https://github.com/tarantool/tarantool/issues/4489
> Branch: olegrok/4489-concat-for-errors
>
> src/lua/error.lua | 11 +++++++
> test/box/misc.result | 75 +++++++++++++++++++++++++++++++++++++++++-
> test/box/misc.test.lua | 24 +++++++++++++-
> 3 files changed, 108 insertions(+), 2 deletions(-)
next prev parent reply other threads:[~2020-01-15 11:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 15:48 olegrok
2020-01-14 14:21 ` Sergey Ostanevich
2020-01-14 15:02 ` Oleg Babin
2020-01-15 11:26 ` Alexander Turenko [this message]
2020-01-15 12:35 ` Oleg Babin
2020-01-16 22:02 ` Alexander Turenko
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=20200115112639.4rlwuxssjcshj65c@tkn_work_nb \
--to=alexander.turenko@tarantool.org \
--cc=babinoleg@mail.ru \
--cc=olegrok@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH v3] error: add __concat method to error object' \
/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