Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:98290 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 35605 invoked from network); 14 Feb 2017 18:30:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Feb 2017 18:30:07 -0000 Authentication-Results: pb1.pair.com smtp.mail=danack@basereality.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=danack@basereality.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain basereality.com from 209.85.213.174 cause and error) X-PHP-List-Original-Sender: danack@basereality.com X-Host-Fingerprint: 209.85.213.174 mail-yb0-f174.google.com Received: from [209.85.213.174] ([209.85.213.174:33457] helo=mail-yb0-f174.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 14/D3-23443-BAC43A85 for ; Tue, 14 Feb 2017 13:30:06 -0500 Received: by mail-yb0-f174.google.com with SMTP id w194so39025531ybe.0 for ; Tue, 14 Feb 2017 10:30:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=basereality-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=n30EeicWqk2Ngevan2AtTL7uTv+1rNWmcEC4W2tTkP0=; b=FQWjekeAGs8eWbx8HF7aDoTpzJBkvtgz4E2whmDwZcgNwFEI5FVlR+JwTgkI1fmTlU HPpIrnKjNO5h0SYFOv2xxiO7en7tIgLNpcRLr3SDNb20PhIFITmziGL68i0alnNNUqfQ yQx4jkIZo9t92AvdUjbwctNyuPiFYudLIS9cejWhMmkzpw92AKlfqqzLq91roEYdX9Eo FWzmKVHXPJO/SdWjSxXOxnXXz3ZWCsQ6Bx6GaD9Yvrpsnt00YjpGp3RMBUPF5tzSPGZf imir3B+n0xXudntvtLfd3ESgVy9sHsTTU9WafECMAsbOowJT5CwJbMssDa9WUHO67xMC GkNw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=n30EeicWqk2Ngevan2AtTL7uTv+1rNWmcEC4W2tTkP0=; b=QLcaZZmd7UE3M2Yd2ckI1fjqgnLQD9eHaXcpaY4vSL+YfI/TdTRjGhaVe75C+mbX0J ilonRPJ7iD+LaKgLiVAWRXucT+IM3HjOgNU514Wb9l/Gyan/7S+45Zm3xQGY2QVA2Tch 1m8H60Dlx1Vu19m+Qhrpa45X/8E9nVZXE2D0OZJj7gCx+ojhwd9/qtqfV/ztTyOX5Awp QY3FZpC6oDqkFyQ4f0q2wqKz37LOa3wkAzvspBzbgh1n5Bn1yrNsLq/7XsNxq4l9Xf7S hTH/pcGtQHNdnFki4aI38mUZ7EOunmmweC+BdQJJj5mx2AzipmYyZs7N1tm9/7SJFQX5 xORg== X-Gm-Message-State: AMke39mn0kClfQZZn4AVG+nsXCSWbrJYn9ItvZP7vJAmDLpq0RCTkyYq9MjL3bdToiqyQJ6JBsoIVJwF3wCFMg== X-Received: by 10.37.170.243 with SMTP id t106mr21947694ybi.171.1487097001107; Tue, 14 Feb 2017 10:30:01 -0800 (PST) MIME-Version: 1.0 Received: by 10.129.50.74 with HTTP; Tue, 14 Feb 2017 10:30:00 -0800 (PST) X-Originating-IP: [212.250.154.206] In-Reply-To: References: Date: Tue, 14 Feb 2017 18:30:00 +0000 Message-ID: To: Niklas Keller Cc: Levi Morrison , "internals@lists.php.net" Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] [RFC][DISCUSSION] Object type hint, now with added variance From: danack@basereality.com (Dan Ackroyd) (resurrecting the thread....) On 24 November 2016 at 09:35, Niklas Keller wrote: > It's not a small amount of complexity, So that other people can understand the tradeoff, please could you detail the complexity as you understand it? > otherwise we'd already have contra / covariance. My understanding is that we already allow this where possible. For example your type-widening RFC https://wiki.php.net/rfc/parameter-no-type-variance What is the problem with allowing it here? cheers Dan