From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> To: olegrok@tarantool.org, tarantool-patches@dev.tarantool.org, imun@tarantool.org Cc: Oleg Babin <babinoleg@mail.ru> Subject: Re: [Tarantool-patches] [PATCH 0/3] lua: table fixes Date: Thu, 13 Feb 2020 23:50:21 +0100 [thread overview] Message-ID: <e3948eec-cc11-1840-ca65-557fb976713e@tarantool.org> (raw) In-Reply-To: <cover.1581625524.git.babinoleg@mail.ru> Hi! Thanks for the patch! On 13/02/2020 21:33, olegrok@tarantool.org wrote: > From: Oleg Babin <babinoleg@mail.ru> > > This patchset fixes three problems. > Two first are bugs in table.deepcopy function. > The third is similar to the second > (because the root of problem is a __pairs > metamethod) that I found then worked on the > second commit. > > Branch: https://github.com/tarantool/tarantool/tree/olegrok/table-fixes Usually we put issue number into branch name. Take a look at branch list on GitHub for examples. Also you need to put web links at the affected issues here. Additionally, we have a new rule, that behaviour changing tickets should be reflected in changelog. This ticket changes behaviour. So you need to add a changelog label. Like this: @ChangeLog - table.deepcopy now correctly handles __metatable attribute of a metatable (gh-4340). I was also thinking about adding a docbot request, but seems like table.* extensions are not documented anyway. > > Oleg Babin (3): > lua: fix incorrect table.deepcopy __metatable handling > lua: table.deepcopy ignores __pairs metamethod > tap: is_deeply ignores __pairs metamethod > > src/lua/table.lua | 9 ++++++-- > src/lua/tap.lua | 9 +++++--- > test/app-tap/table.test.lua | 44 ++++++++++++++++++++++++++++++++++++- > test/app-tap/tap.result | 6 +++-- > test/app-tap/tap.test.lua | 24 +++++++++++++++++++- > 5 files changed, 83 insertions(+), 9 deletions(-) >
next prev parent reply other threads:[~2020-02-13 22:50 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-02-13 20:33 olegrok 2020-02-13 20:33 ` [Tarantool-patches] [PATCH 1/3] lua: fix incorrect table.deepcopy __metatable handling olegrok 2020-02-13 22:50 ` Vladislav Shpilevoy 2020-02-20 11:12 ` Igor Munkin 2020-02-13 20:33 ` [Tarantool-patches] [PATCH 2/3] lua: table.deepcopy ignores __pairs metamethod olegrok 2020-02-13 22:50 ` Vladislav Shpilevoy 2020-02-20 11:00 ` Igor Munkin 2020-02-13 20:33 ` [Tarantool-patches] [PATCH 3/3] tap: is_deeply " olegrok 2020-02-13 22:50 ` Vladislav Shpilevoy 2020-02-20 10:57 ` Igor Munkin 2020-02-13 22:50 ` Vladislav Shpilevoy [this message] 2020-02-15 10:05 ` [Tarantool-patches] [PATCH 0/3] lua: table fixes Oleg Babin 2020-02-15 15:35 ` 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=e3948eec-cc11-1840-ca65-557fb976713e@tarantool.org \ --to=v.shpilevoy@tarantool.org \ --cc=babinoleg@mail.ru \ --cc=imun@tarantool.org \ --cc=olegrok@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 0/3] lua: table fixes' \ /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