Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:93330 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 60944 invoked from network); 14 May 2016 12:32:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 May 2016 12:32:01 -0000 Authentication-Results: pb1.pair.com header.from=danack@basereality.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=danack@basereality.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain basereality.com from 209.85.213.47 cause and error) X-PHP-List-Original-Sender: danack@basereality.com X-Host-Fingerprint: 209.85.213.47 mail-vk0-f47.google.com Received: from [209.85.213.47] ([209.85.213.47:33497] helo=mail-vk0-f47.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1F/51-48938-0CA17375 for ; Sat, 14 May 2016 08:32:01 -0400 Received: by mail-vk0-f47.google.com with SMTP id z184so13031411vkg.0 for ; Sat, 14 May 2016 05:32:00 -0700 (PDT) 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:date:message-id:subject:from:to :cc; bh=xKNGAuDV0sFEPwT4iAcvP3wsa8N4/NGkeJ09cwPLvEE=; b=dhH7PIrNDxzS3ItXIrDOxWtyqA7zcUc3bLAcnOQHF1pGAATJDOl1WZj5GtBgHqHlFv sqJg59BP8tkt1XKTE1nJ7UAXG+41dixijNsL/DGEv6QrL6OjNq3m46LW1kR27kY8j+QM Vzsv077n3j9rxlTcwOq7BfdB5XNVA2/x1BoSxsvCS6fdwS6ggEhc0SjZfChdJjUo9+3N iTnvmotYF04t42cDL3pu4TPpb+9RPQdXpo570PEc05KJ49sbNrZ9d8p6xUo2tyktJZU7 dGly8td7tUd7nMTyCoe3Y5UHAU6wskVtp8S+QQ9HfrVPCYL5gRY5whN9t2CN++zZ4+zH rUyQ== 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; bh=xKNGAuDV0sFEPwT4iAcvP3wsa8N4/NGkeJ09cwPLvEE=; b=KVUq8K89+msuz0iCvuu0JwcJ8jHjcZKFhoiYWYPhmNmnldp3BUxNxEAimHS8hBL9n2 T69BPxFYRn10qIkvA0z7/Rs9rj0wyKZVuHpfNo96O+ICTWXMaPh/DGFZhbLhPZ8YY9qw fHixZYbQmz1JdDmjN2YhfT0fMRNjJTpo/0Xlhw4lc1s40NssZbZUuCISfQlo6zbUfh0m V1PfEYLisq4uU/h8LGM4/+a/axpX74UAFwZQQYbstS1pS10nnRoX9qPWA6w1dXaNEseV YNIepMF1701ZZaGT/iR7BFP27p3AKYrtBvvGtUURB5iggmTxAYhdFMFAQFuvjal2Hj86 RL2g== X-Gm-Message-State: AOPr4FV0P9XAQTB180t0XTS0PrIbd5QqcL1R2mvTlxn8/i0BvsJzua84CZtobAFPT09nfcl9pmtXN1mUdelVnw== MIME-Version: 1.0 X-Received: by 10.31.167.10 with SMTP id q10mr9181543vke.44.1463229117672; Sat, 14 May 2016 05:31:57 -0700 (PDT) Received: by 10.176.69.231 with HTTP; Sat, 14 May 2016 05:31:57 -0700 (PDT) X-Originating-IP: [78.149.15.25] In-Reply-To: References: Date: Sat, 14 May 2016 13:31:57 +0100 Message-ID: To: Rasmus Schultz Cc: Benjamin Eberlei , PHP internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] [RFC] Simple Annotations From: danack@basereality.com (Dan Ackroyd) On 14 May 2016 at 12:48, Rasmus Schultz wrote: > > Hack's memoize is an annotation for the language interpreter itself - > that's beyond the scope of this RFC, but could be implemented in the > future. Please can you add something to the RFC that reserves the possibility to do this, so that it can be introduced in a BC compatible way in the future? Hand-waving away problems and saying that they aren't in scope is a sure-fire way to build deficiencies into a design. This is not a smaller problem in userland code, as it is easy for people to migrate from one library to another, but is almost impossible to overcome in core PHP, where any BC-breaking change causes lots of difficultly for end-users. cheers Dan