Tarantool development patches archive
 help / color / mirror / Atom feed
From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: tarantool-patches@freelists.org,
	AKhatskevich <avkhatskevich@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH v2][vshard] Check self passed to object methods
Date: Mon, 4 Jun 2018 15:12:22 +0300	[thread overview]
Message-ID: <0ee4cf31-6134-80d7-e610-85c75194ea70@tarantool.org> (raw)
In-Reply-To: <20180604111226.8446-1-avkhatskevich@tarantool.org>

Pushed with my minor fixes.

On 04/06/2018 14:12, AKhatskevich wrote:
> Changes:
> 
> 1. `check_self_arg` function wrapper added to utils.
> Its mechanics:
>   * check that the first argument has expected metatable
>   * return result of a real function
> 
> 2. Check, that self argument is passed to all replicaset and replica
> object methods.
> 
> Closes: #81
> ---
> Branch: https://github.com/tarantool/vshard/tree/kh/gh-81-wo-mt-sort
> Issue: https://github.com/tarantool/vshard/issues/81
> 

      reply	other threads:[~2018-06-04 12:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-04 11:12 [tarantool-patches] " AKhatskevich
2018-06-04 12:12 ` Vladislav Shpilevoy [this message]

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=0ee4cf31-6134-80d7-e610-85c75194ea70@tarantool.org \
    --to=v.shpilevoy@tarantool.org \
    --cc=avkhatskevich@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='[tarantool-patches] Re: [PATCH v2][vshard] Check self passed to object methods' \
    /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