Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:92273 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 67832 invoked from network); 14 Apr 2016 03:42:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Apr 2016 03:42:30 -0000 Authentication-Results: pb1.pair.com header.from=morrison.levi@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=morrison.levi@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.67 as permitted sender) X-PHP-List-Original-Sender: morrison.levi@gmail.com X-Host-Fingerprint: 209.85.220.67 mail-pa0-f67.google.com Received: from [209.85.220.67] ([209.85.220.67:35466] helo=mail-pa0-f67.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0C/70-60797-4A11F075 for ; Wed, 13 Apr 2016 23:42:28 -0400 Received: by mail-pa0-f67.google.com with SMTP id zy2so5614660pac.2 for ; Wed, 13 Apr 2016 20:42:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=n8+EKKppG+hTueKEJXH3t68CoMuaTOPnKdclhDbK7h8=; b=nZ8KJnW3HSUJ2nSwq/jATJyYiRJdSs7iF/l4HqplabjGtVNRQf+w9rGW2kCeMxc+Ns 0riHbxIIw95pFcdt5T25XnAUwlNuAB3/Lg7wWtpip9xlehEvAkWIxK+9ZRDtZA/GF+JL v1e3sKYNnWZyibbWx1xc9XB/PZw+2N65HEekbtijomafpmws27HIXT/+/NznTFc6tL7O /Vcu20rfB7S1KKY/KCLhCC5Ds3pWknHhqiBeJJsk9kuUYE4IMLUcVibl814Cgb7euFRZ oHCTK4PEfGuGWrTwWpeVCzf3RcewtCe0+fFQjh9HeF5XXjw+qN8Y+8zt5MaWzz7dpUF/ noAQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=n8+EKKppG+hTueKEJXH3t68CoMuaTOPnKdclhDbK7h8=; b=AA1vN2UYVlQncCssreL38PiYlR9Gbdh3jBT4L7wyCRq+o9C4T+lUOSEN+PRPTOm5iV VlAOMNJmHu/yAC0FBAv9iDKfUIPSEWbO2zKOacRMNgXZFrF/XPccA9x8gTH2ZydJljuc gXtHZsGdMMYcewjz6Pv6E40enRI3Pi2wC1NxkNhYFVIRKBt1szXRVH7tffY2pPgXvQwP TShBAXZltDIz7NJ3NQ1iBVLuFH7Vsqv8l/ZlUJTvhko9NCX1yoHg8NumzaZR73wJaRpU FKPLAsfwPn8RXPIVKbwOIhLum2jyqYJsrHv9hsdrLWNe1gT6oPvyh957y/f3C/u1tWHy V23w== X-Gm-Message-State: AOPr4FXAWYUeWdbNV7VNwrQMKVQaLbY07K8TMiqKjwkL9DVk0k6YwijVtZQzBsyaDQ8n+ZsQWeZTQ+5dNWIHRg== MIME-Version: 1.0 X-Received: by 10.66.232.4 with SMTP id tk4mr18043126pac.103.1460605345304; Wed, 13 Apr 2016 20:42:25 -0700 (PDT) Received: by 10.66.163.232 with HTTP; Wed, 13 Apr 2016 20:42:25 -0700 (PDT) Date: Wed, 13 Apr 2016 21:42:25 -0600 Message-ID: To: internals Content-Type: text/plain; charset=UTF-8 Subject: [RFC] Nullable Types From: morrison.levi@gmail.com (Levi Morrison) As alluded to in an earlier email today[1] I am now moving the Nullable Types RFC[2] to the discussion phase. In a nutshell this RFC proposes syntax for declaring a type to alternatively be null. There is a decision that needs to be made: does the question mark go before or after the type name? function (?Foo $foo); function (Foo? $foo); There are precedents in several languages for each position. Some relevant issues to where the question mark goes are noted in the RFC[3]. I look forward to a helpful and meaningful discussion! [1]: http://news.php.net/php.internals/92252 [2]: https://wiki.php.net/rfc/nullable_types [3]: https://wiki.php.net/rfc/nullable_types#position_of