From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-f194.google.com (mail-lj1-f194.google.com [209.85.208.194]) (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 611B64696C3 for ; Fri, 10 Apr 2020 11:17:20 +0300 (MSK) Received: by mail-lj1-f194.google.com with SMTP id k21so1216013ljh.2 for ; Fri, 10 Apr 2020 01:17:20 -0700 (PDT) Date: Fri, 10 Apr 2020 11:17:17 +0300 From: Cyrill Gorcunov Message-ID: <20200410081717.GL3072@uranus> References: <328813debe7020378d0faa79bc3eee8cd00f6197.1586486220.git.alexander.turenko@tarantool.org> <20200410080513.GA32010@atlas> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200410080513.GA32010@atlas> Subject: Re: [Tarantool-patches] [PATCH 12/13] coio: add *_noxc read / write functions List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Konstantin Osipov Cc: tarantool-patches@dev.tarantool.org On Fri, Apr 10, 2020 at 11:05:13AM +0300, Konstantin Osipov wrote: > > > > +/* > > + * FIXME: Rewrite coio_read_ahead_timeout() w/o C++ exceptions and > > + * drop this function. > > + */ > > Ugh. > > Why can't you do it instead? This is necessary for a lot of other > patches, I believe Georgy's patches are doing it as well. Simply because we want a functional popen engine in the upcoming release. We gonna cleanup/fixup and etc in next iteration. And unweaving service functions from exception is nontrivial. As to me such things should be done by separate series. If you take a look on Georgy's patches with more attention you'll see that the changes are far more than just modifying the helpers, they affect context.