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 66CEC46970E for ; Wed, 5 Feb 2020 14:09:46 +0300 (MSK) Received: by mail-lj1-f195.google.com with SMTP id q8so1849333ljj.11 for ; Wed, 05 Feb 2020 03:09:46 -0800 (PST) Date: Wed, 5 Feb 2020 14:09:44 +0300 From: Konstantin Osipov Message-ID: <20200205110944.GA9833@atlas> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Tarantool-patches] [PATCH v2 0/4] Don't truncate float in update List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vladislav Shpilevoy Cc: tarantool-patches@dev.tarantool.org * Vladislav Shpilevoy [20/02/05 01:53]: > The patchset fixes float value truncation in > tuple/space:update/upsert. First commit fixes the actual issue, > but introduces another bug that a float value can be stored into a > field having double type in its format. Thanks for CCing. While I find the general idea of the series quite nice, I don't know why it's a priority. Did anyone actually complain? PS Would be best if you don't Cc/To me with the entire series next time, but @mention me on the list if you would like to get my review. I am reading all patches on the list anyway, no need to copy them to my inbox. -- Konstantin Osipov, Moscow, Russia