Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118644 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 95166 invoked from network); 16 Sep 2022 17:52:52 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 16 Sep 2022 17:52:52 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 5802D180384 for ; Fri, 16 Sep 2022 10:52:51 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: *** X-Spam-Status: No, score=3.2 required=5.0 tests=BAYES_20, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_SOFTFAIL,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-yw1-f176.google.com (mail-yw1-f176.google.com [209.85.128.176]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Fri, 16 Sep 2022 10:52:50 -0700 (PDT) Received: by mail-yw1-f176.google.com with SMTP id 00721157ae682-333a4a5d495so268408767b3.10 for ; Fri, 16 Sep 2022 10:52:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=ICvNgkLy3uG3hTv8/LemGwDyeZD3cYyHFIgYa0v2zJA=; b=HPMM1lMH88T7r303m0Z5ZfXXhOGrRDho5P+U7dGl2me5PZkUFi8YZg5ypEm7Ezvgme o0IzdPBzFyub/QWxCv5rmtUXpUpUORwNoPBzZ8XWLvPCfnmxlzxSuEWrGRHEZuc6oEln Fq2Ztd/nh6++x1YUYoALQDAjxm8piExMMn1Q5izbM8eiXqZ50NSf2pxQsYSWWBMFRayV 0x27jeYJsZEtdm0NCobO/NB/6Sy8FTpp1h+LoM0SFhPRlgMSzLCyl1dywkkKDl/X1ehH pQTDUZl6qsyXXSqF3p5xz34p8HJL4nRxnt+OTFynpcNVzTKRMHyBeRrIo/obB+uH0/En 68xA== X-Gm-Message-State: ACrzQf23HswBUEefU1LWczZ0eHDISpDqizwQltCN4/kf+ZFgMzyf8E0c lkoCuFrcYYUFZsI3tLyOY3KCq7mrYXS+AL2a3F/yjKehRbq7nA== X-Google-Smtp-Source: AMsMyM5xkl9rBY1tswVbU3qyqpNsQv3UucDw0DX+qZ+jOpKRPdgyYh995E7RHM6O0/rMV8vnBakbVpfXhQ8pd9p6QWs= X-Received: by 2002:a81:86c2:0:b0:332:a104:f7e4 with SMTP id w185-20020a8186c2000000b00332a104f7e4mr5413965ywf.505.1663350770312; Fri, 16 Sep 2022 10:52:50 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Fri, 16 Sep 2022 12:52:39 -0500 Message-ID: To: Paul Dragoonis Cc: Timmy Almroth , PHP Internals List Content-Type: multipart/alternative; boundary="000000000000cd3b3505e8cf0725" Subject: Re: [PHP-DEV] RFC: StreamWrapper Support for glob() From: pollita@php.net (Sara Golemon) --000000000000cd3b3505e8cf0725 Content-Type: text/plain; charset="UTF-8" Couldn't find the original message to reply to, but #1 I'd like to see the RFC actually fleshed out. There's a PR linked, but we should define the actual goals/APIs etc... in the RFC itself as well as the numerous edge cases Christophe noted and why they aren't (or are?) concerns. I do recall discussing this with Wez many years ago and the sharp corners felt like a "wait until someone is asking for it" kind of situation. -Sara --000000000000cd3b3505e8cf0725--