Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:92978 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 6258 invoked from network); 30 Apr 2016 10:51:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Apr 2016 10:51:44 -0000 Authentication-Results: pb1.pair.com smtp.mail=php@tutteli.ch; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=php@tutteli.ch; sender-id=pass Received-SPF: pass (pb1.pair.com: domain tutteli.ch designates 80.74.144.14 as permitted sender) X-PHP-List-Original-Sender: php@tutteli.ch X-Host-Fingerprint: 80.74.144.14 ns10.kreativmedia.ch Received: from [80.74.144.14] ([80.74.144.14:35333] helo=ns10.kreativmedia.ch) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 14/D6-58459-D3E84275 for ; Sat, 30 Apr 2016 06:51:42 -0400 Received: from RoLaptop (adsl-84-227-2-98.adslplus.ch [84.227.2.98]) by ns10.kreativmedia.ch (Postfix) with ESMTPSA id B502E47E10B9; Sat, 30 Apr 2016 12:51:37 +0200 (CEST) To: "'Rasmus Schultz'" Cc: "'Josh Di Fabio'" , "'Dominic Grostate'" , "'Guilherme Blanco'" , "'Mathieu Rochette'" , "'Ben Scholzen 'DASPRiD''" , "'Sara Golemon'" , "'PHP internals'" , "'Mathieu Rochette'" References: <3cc8a4c7-2640-11ae-a67b-06f909ac1e27@texthtml.net> <57173859.4080501@rochette.cc> <013101d19ff8$596b6010$0c422030$@tutteli.ch> In-Reply-To: Date: Sat, 30 Apr 2016 12:51:36 +0200 Message-ID: <018e01d1a2ce$449679d0$cdc36d70$@tutteli.ch> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQIuz2pO4BlNO6AEdNznmEmHKOSPUgH8tzyzAcTvi2ACWFsrBwIO1wFmAdxRi5QCZxtKUgESOGzrAqPTpEkCRZ9CuAKMyUA5AeMzfRMCUYkuygGCWeQ3AazbulWeBTZsIA== Content-Language: de-ch Subject: AW: [PHP-DEV] [RFC:generics] From: php@tutteli.ch ("Robert Stoll") > > In this case I would suggest to use class A which leaves = room > > open to define lower bounds later on >=20 > IMHO that is bordering on unreadable - all those brackets are really = confusing and hard on the eyes. >=20 I agree, it looks quite ugly :-)=20 Therefore another suggestion: class A [Foo <: T1, T2 <: Bar] { //.... } > Either way, using : does not prevent us from adding lower bounds later = on - but even then, upper bound is the 99% use > case, so I don't think it makes sense to design the syntax around a = possible future upper bound. >=20 > If we do support it in the future, I don't think anyone's going to = care what it looks like, as it's unlikely most people will ever > encounter it or need it. >=20 You're probably right. I use wildcard types with lower bounds in Java = from time to time but rather rarely.=20