Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:81792 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 72923 invoked from network); 4 Feb 2015 09:22:26 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Feb 2015 09:22:26 -0000 Authentication-Results: pb1.pair.com smtp.mail=dmitry@zend.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=dmitry@zend.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.220.179 as permitted sender) X-PHP-List-Original-Sender: dmitry@zend.com X-Host-Fingerprint: 209.85.220.179 mail-vc0-f179.google.com Received: from [209.85.220.179] ([209.85.220.179:38942] helo=mail-vc0-f179.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 65/D3-55046-1D4E1D45 for ; Wed, 04 Feb 2015 04:22:26 -0500 Received: by mail-vc0-f179.google.com with SMTP id la4so137343vcb.10 for ; Wed, 04 Feb 2015 01:22:21 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=DX0toWwKKpBBzxSNO8LGIMcm27gXy+veLsAxp3WfvJo=; b=DzWHQS8UPxTkBch003vrt75I9rO3erWWO6W/RuOLpYpJ6hloFKFZKV1zxM8GDkUpI2 7L7duLn1Qer0XKpzZpVsO0xLbCrTP9VYaVX4e55FlF2ekQHTENhVGfEW19/vIrIEld7c lkoYF+eYaMLwC4koUANGeWGvqB50INDHiu+1gJC1efJ3wQdIujCiaxwHYoLL9Zzam+jy D6E9/R3Ie8zL3tpvZ0MkX/u7DNuiPj4mfnN32sxeMzX+nkBFpT4ZCNoGYv8rTYut/Vvj xK9tLOrzW9j1w58XJJrWgATQKUwaHVF9bPrEU6SNNl3YvEjeiNNhYjc7dCRLR/b5p4D0 Vxug== X-Gm-Message-State: ALoCoQmmcRndMoi6jrKa1D5CEVXh0bfXDnrrrkLw6CQH1VTXU+TrQkGL4G5bSwmj5ICp+DIoikfjug4DCWxbX5IW4QHK/JsH5xt0VIW7nQ82sZyIoeKGQDXl9Z7Tn5dx1oXKS7zc0beWL4niyKluu8b+7Y7r+qrsmg== MIME-Version: 1.0 X-Received: by 10.52.103.75 with SMTP id fu11mr15914997vdb.5.1423041741840; Wed, 04 Feb 2015 01:22:21 -0800 (PST) Received: by 10.52.74.73 with HTTP; Wed, 4 Feb 2015 01:22:21 -0800 (PST) In-Reply-To: References: <00c101d04049$ca411ec0$5ec35c40$@tekwire.net> Date: Wed, 4 Feb 2015 13:22:21 +0400 Message-ID: To: Yasuo Ohgaki Cc: =?UTF-8?Q?Fran=C3=A7ois_Laupretre?= , Joe Watkins , PHP Internals , Andrea Faulds , Nikita Popov Content-Type: multipart/alternative; boundary=047d7b86d99085fead050e3fb9c7 Subject: Re: [PHP-DEV] What do we need strict scalar type hints for? From: dmitry@zend.com (Dmitry Stogov) --047d7b86d99085fead050e3fb9c7 Content-Type: text/plain; charset=UTF-8 I mean a lot of work designing this concept properly, writing RFC, discussing, coming to consensus, etc The implementation itself may be quite simple. If anyone can take care about design, I may help with implementation. Thanks. Dmitry. On Wed, Feb 4, 2015 at 12:02 PM, Yasuo Ohgaki wrote: > Hi Dmitry, > > On Wed, Feb 4, 2015 at 4:25 PM, Dmitry Stogov wrote: > >> The idea of that RFC was an ability to have zero-cost assert(). >> >> DbC is a much more bigger feature, it is interesting, but requires >> significant work. > > > Type check and DbC integration would require significant work, I guess. > If you say so, it is. > > How about simple in{}, out{} block? I expect it's much simpler. > Injecting in{} and out{} block code to before/after execute() something > like this. > If execute() is replaceable as before, then we may have two execute() > for production and development. There will be zero performance cost > hopefully. > > Regards, > > -- > Yasuo Ohgaki > yohgaki@ohgaki.net > --047d7b86d99085fead050e3fb9c7--