On 18.08.20 00:03, Benas IML wrote:
And then boo-yah, 6 months later we want to implement a cool new
feature to
attributes (a lot of examples were said before, ain't repeating myself) but
we can't :(( because there is no ending delimiter and thus, we will run
into parsing issues.
Both @{} and
On Sun, Aug 16, 2020 at 11:36 AM Benjamin Eberlei wrote:
>
> We have updated the RFC with all (hopefully) of the feedback from this
> discussion:
>
> https://wiki.php.net/rfc/shorter_attribute_syntax_change
>
> Most notable changes are:
> - A new section with several subsections on the benefits
On Tue, Aug 18, 2020, 12:56 AM Jakob Givoni wrote:
> On Sun, Aug 16, 2020 at 11:36 AM Benjamin Eberlei
> wrote:
> >
> > We have updated the RFC with all (hopefully) of the feedback from this
> > discussion:
> >
> > https://wiki.php.net/rfc/shorter_attribute_syntax_change
> >
> > Most notable
Hi Benas,
On Mon, Aug 17, 2020 at 11:34 PM Benas IML wrote:
>
> On Tue, Aug 18, 2020, 12:25 AM Jakob Givoni wrote:
>>
>> The question is now if it's reasonable at all to change something for
>> 99% purely subjective reasons (no other substantial fact has been put
>> forward other than the VIM
I have been following all the lengthy discussions on this topic hoping the list
would come to consensus. And I had been hoping someone would call the following
question but since no one else has here goes.
The concept of adding attributes to PHP seemed to sail to acceptance but, if
you count
On Sun, Aug 16, 2020 at 11:32 AM Benjamin Eberlei wrote:
>
> On Sun, Aug 16, 2020 at 10:39 AM Jakob Givoni wrote:
>>
>> Hi Benjamin,
>>
>> I'm sorry, but I don't understand your argument.
>> It's true that annotations used to be enclosed in a docblock, but that
>> is not an argument for saying
Hi Rowan,
On 21/05/2020 23:53, Rowan Tommins wrote:
> d) Support "chunked" transfer encoding (RFC 7230 Section 4.1)
FWIW, I've just been hit by https://bugs.php.net/bug.php?id=47021 in a
SOAP response from a server using "Transfer-Encoding:chunked". I see the bug is still open, although the
On Tue, Aug 18, 2020, 12:25 AM Jakob Givoni wrote:
> On Sun, Aug 16, 2020 at 11:32 AM Benjamin Eberlei
> wrote:
> >
> > On Sun, Aug 16, 2020 at 10:39 AM Jakob Givoni wrote:
> >>
> >> Hi Benjamin,
> >>
> >> I'm sorry, but I don't understand your argument.
> >> It's true that annotations used to
On Tue, Aug 18, 2020, 1:04 AM Jakob Givoni wrote:
> Hi Benas,
>
> On Mon, Aug 17, 2020 at 11:34 PM Benas IML
> wrote:
> >
> > On Tue, Aug 18, 2020, 12:25 AM Jakob Givoni wrote:
> >>
> >> The question is now if it's reasonable at all to change something for
> >> 99% purely subjective reasons
"Lokrain" lokr...@gmail.com – August 17, 2020 7:14 PM
>
>
> On Mon, 17 Aug 2020 at 19:46, Mathieu Rochette
> wrote:
>
>
>> Hi,
>>
>>
>>
>> I’m writing a message here to receive feedback on a two ideas related
to
>> class constructors before going more in details with an RFC. I hope
Thanks Rowan. I can appreciate that rationale.
Also let’s me in on why we might want to have an indexed array that is not
necessarily sequential - but are integers.
Thanks again.
Cheers,
Josh
> On Aug 17, 2020, at 4:17 AM, Rowan Tommins wrote:
>
> On Mon, 17 Aug 2020 at 05:19, Michael
Hi Rowan
> On 14/08/2020 17:14, Ilija Tovilo wrote:
>> I've been thinking about ways to improve string interpolation. String
>> interpolation in PHP is currently pretty limited to say the least.
Thanks for your feedback!
> we could take the opportunity to bring more features into the mix
>
> 1)
Hi Alex
>> I've been thinking about ways to improve string interpolation.
>
> Using a prefix for strings that have a saner interpretation reminds me of
> f-strings in python 3. I would suppose you know about it already but I'll
> leave a link here anyway:
On Sun, 16 Aug 2020 at 10:29, Benjamin Eberlei wrote:
> We have updated the RFC at
> https://wiki.php.net/rfc/shorter_attribute_syntax_change with what we
> think
> covers all the discussion and arguments made in this and the previous
> mailing list threads.
>
Thank you for putting in the work
(Resending, as my @php.net email address never makes it to the list)
On Sun, 16 Aug 2020 at 07:42, Jakob Givoni wrote:
> Can I make a suggestion?
>
> Make the new or updated RFC a primary vote on: "Should attributes be
> enclosed in delimiters?"
> This is what we're really discussing and that
On Mon, 17 Aug 2020 at 02:06, Theodore Brown wrote:
> ## Forcing @@ attributes to end with parenthesis?
>
> I don't really see the point of this section in the RFC.
The blame for that is on me, not Benjamin and Derek, as I repeatedly asked
why a compulsory ) could not be considered a closing
On Mon, 17 Aug 2020 at 05:19, Michael Voříšek - ČVUT FEL <
voris...@fel.cvut.cz> wrote:
> This seems almost as a bug, strict types should apply also for array key
> which is currently not the case.
>
> https://3v4l.org/epv5s
No, it really shouldn't. In hindsight, "strict_types" was a bad name
As a possible addition/discussion point, I only noticed today that @{}
is a syntax that has not been mentioned yet, also not in any previous
discussions about attributes as far as I can tell. @{} currently leads
to a syntax error, so there is no BC break, and {} is common syntax for
grouping
On Sun, Aug 16, 2020 at 12:36 PM Benjamin Eberlei wrote:
>
> We have updated the RFC with all (hopefully) of the feedback from this
> discussion:
>
> https://wiki.php.net/rfc/shorter_attribute_syntax_change
>
> Most notable changes are:
> - A new section with several subsections on the benefits
On Mon, Aug 17, 2020 at 3:06 AM Theodore Brown
wrote:
> On Sun, Aug 16, 2020 at 4:36 AM Benjamin Eberlei
> wrote:
>
> > We have updated the RFC with all (hopefully) of the feedback from
> > this discussion:
> >
> > https://wiki.php.net/rfc/shorter_attribute_syntax_change
> >
> > Most notable
On Mon, Aug 17, 2020 at 2:29 PM Benjamin Eberlei
wrote:
>
>
> On Mon, Aug 17, 2020 at 10:02 AM Peter Bowyer wrote:
>
>> On Sun, 16 Aug 2020 at 10:29, Benjamin Eberlei
>> wrote:
>>
>>> We have updated the RFC at
>>> https://wiki.php.net/rfc/shorter_attribute_syntax_change with what we
>>> think
On Mon, Aug 17, 2020 at 10:59 AM Alexandru Pătrănescu
wrote:
> On Sun, Aug 16, 2020 at 12:36 PM Benjamin Eberlei
> wrote:
> >
> > We have updated the RFC with all (hopefully) of the feedback from this
> > discussion:
> >
> > https://wiki.php.net/rfc/shorter_attribute_syntax_change
> >
> > Most
On Mon, Aug 17, 2020 at 7:11 AM Benjamin Eberlei wrote:
> On Mon, Aug 17, 2020 at 3:06 AM Theodore Brown wrote:
> > However, ending delimiters in PHP have little to do with how "complex"
> > a syntax construct is (which is a rather loose definition, anyway).
> > As I've pointed out before,
On Mon, Aug 17, 2020, 4:07 PM Theodore Brown wrote:
> On Mon, Aug 17, 2020 at 7:11 AM Benjamin Eberlei
> wrote:
>
> > On Mon, Aug 17, 2020 at 3:06 AM Theodore Brown
> wrote:
> > > However, ending delimiters in PHP have little to do with how "complex"
> > > a syntax construct is (which is a
possibility to keep @@ and add @{} as a second syntax for attributes
+1, but I would keep same prefix, ie. @@{} (or @@[]), for both syntaxes,
it is much easier for human eyes to search for one thing, also easier
for grep
With kind regards / Mit freundlichen Grüßen / S přátelským pozdravem,
On Mon, 17 Aug 2020 at 16:21, Matteo Beccati wrote:
> Hi Rowan,
>
> On 21/05/2020 23:53, Rowan Tommins wrote:
> > d) Support "chunked" transfer encoding (RFC 7230 Section 4.1)
>
> FWIW, I've just been hit by https://bugs.php.net/bug.php?id=47021 in a
> SOAP response from a server using
Hi,
I’m writing a message here to receive feedback on a two ideas related to
class constructors before going more in details with an RFC. I hope this is
appropriate behavior for this list
With the Constructor Property Promotion accepted in PHP 8, there’s a lot
less of boilerplate when
On Mon, 17 Aug 2020 at 19:46, Mathieu Rochette wrote:
> Hi,
>
>
>
> I’m writing a message here to receive feedback on a two ideas related to
> class constructors before going more in details with an RFC. I hope this is
> appropriate behavior for this list
>
>
>
> With the Constructor Property
Interesting stuff!
https://wiki.php.net/rfc/constructor_promotion
I see this for the first time, but I like it :)
Now to your proposal.
Just to make sure I understand:
Would this map the parameters by name or by index?
-> I assume by index, it makes more sense.
Does it map to parent constructor
On Sun, Aug 16, 2020 at 4:47 PM tyson andre
wrote:
> Hi Benjamin,
>
> > We are looking for further feedback from the community.
>
> Thanks, the updated RFC looks much better.
> Some more feedback on why the edge cases are a concern to me,
> and why the lack of an ending delimiter is similar to
On Mon, Aug 17, 2020 at 10:02 AM Peter Bowyer wrote:
> On Sun, 16 Aug 2020 at 10:29, Benjamin Eberlei
> wrote:
>
>> We have updated the RFC at
>> https://wiki.php.net/rfc/shorter_attribute_syntax_change with what we
>> think
>> covers all the discussion and arguments made in this and the
On Mon, Aug 17, 2020 at 5:
14 PM Theodore Brown wrote:
> On Mon, Aug 17, 2020 at 8:07 AM Theodore Brown
> wrote:
>
> > On Mon, Aug 17, 2020 at 7:11 AM Benjamin Eberlei
> wrote:
> > > On Mon, Aug 17, 2020 at 3:06 AM Theodore Brown
> wrote:
> > > > ## Potential Future Benefits of Enclosed
On Mon, Aug 17, 2020, at 7:30 AM, Michael Voříšek - ČVUT FEL wrote:
> > possibility to keep @@ and add @{} as a second syntax for attributes
>
> +1, but I would keep same prefix, ie. @@{} (or @@[]), for both syntaxes,
> it is much easier for human eyes to search for one thing, also easier
> for
On Mon, Aug 17, 2020 at 10:21 AM Benjamin Eberlei wrote:
> On Mon, Aug 17, 2020 at 5:14 PM Theodore Brown wrote:
> > On Mon, Aug 17, 2020 at 8:07 AM Theodore Brown wrote:
> > > On Mon, Aug 17, 2020 at 7:11 AM Benjamin Eberlei wrote:
> > > > On Mon, Aug 17, 2020 at 3:06 AM Theodore Brown wrote:
>
On Sun, Aug 16, 2020 at 4:29 AM Benjamin Eberlei
wrote:
> Following the valid criticisms of us starting the vote too early, we have
> closed the vote for this RFC for now.
>
> We look to restart the vote middle next week, so that we can close this
> before the Beta 3 release on September 3rd.
>
On Mon, Aug 17, 2020 at 8:07 AM Theodore Brown wrote:
> On Mon, Aug 17, 2020 at 7:11 AM Benjamin Eberlei wrote:
> > On Mon, Aug 17, 2020 at 3:06 AM Theodore Brown
> > wrote:
> > > ## Potential Future Benefits of Enclosed Delimiter Syntax?
> > >
> > > The RFC shows an example of a potential
36 matches
Mail list logo
