From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-f195.google.com (mail-lj1-f195.google.com [209.85.208.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id D67774696C3 for ; Wed, 15 Apr 2020 19:09:05 +0300 (MSK) Received: by mail-lj1-f195.google.com with SMTP id j3so3850196ljg.8 for ; Wed, 15 Apr 2020 09:09:05 -0700 (PDT) Date: Wed, 15 Apr 2020 19:09:02 +0300 From: Konstantin Osipov Message-ID: <20200415160902.GA21441@atlas> References: <20200415141359.16253-1-gorcunov@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200415141359.16253-1-gorcunov@gmail.com> Subject: Re: [Tarantool-patches] [PATCH] vclock: rename vclock_reset to vclock_set List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Cyrill Gorcunov Cc: tml * Cyrill Gorcunov [20/04/15 17:16]: > The `reset` keyword is too overloaded, its traditional > context is to setup some value either to zero or to default. > > That is not what we're doing in this helper: we rather set up > a new value to the replica_id in the map, keeping consistency > of the sum. > Thus lets name it as it should -- vclock_set. Well, one could argue that it's impossible to set a vclock component without violating consistency - vclock should never go back. reset() indicates that it can unwind the clock. -- Konstantin Osipov, Moscow, Russia