On Fri, Jun 13, 2025, at 6:33 AM, 'Andreas Heigl' via PHP Framework 
Interoperability Group wrote:


> So all in all:
>
> I did not hear anyone saying that it is a bad idea which implies that 
> the idea has some merits.
>
> We have 4 people that are willing to form an initial Working Group 
> (Juliette, Jaap, Vincent and myself), one of which (Vincent) offered to 
> be the CC sponsor. Per the bylaws that right now would not be sufficient 
> for a full working group but definitely for a limited Working Group
>
> As the scope will definitely evolve over time and is not expected to be 
> actually finished at one point this sounds more like it fits the PER 
> process.
>
> The proposal seems to be to define and maintain a set of attributes that 
> are relevant for more than one single tool so that different tools can 
> use and rely upon a defined set of attributes and users do not need to 
> use several similar attributes with the same meaning for different 
> tools. The expected outcome is a meta-document listing the attributes, 
> possible parameters to them and a usage for each of them. In addition a 
> package will be distributed that contains implementations for these 
> attributes to support usage in code or auto-complete.
>
> Any additions to this? Any Objections?
>
> Cheers
>
> Andreas

I want to reiterate my earlier point:

A PER whose artifact is a markdown file:

* Pure - Indicates a function with no side effects.
* Internal - Indicates a function that should not be used outside this library

is, IMO, unuseful and potentially even counter productive, and I would not 
support or participate in it.

A PER whose artifact is a repository with the following in it:

namespace Fig\Attributes;

// Indicates a function with no side effects.
#[Attribute]
class Pure {}

// Indicates a function that should not be used outside this library
#[Attribute]
class Internal {}

I believe would be useful, and I would support it and be interested in joining 
it.  

(Naturally some attributes will also have parameters, some not, that's a case 
by case to figure out later.)

--Larry Garfield

-- 
You received this message because you are subscribed to the Google Groups "PHP 
Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to php-fig+unsubscr...@googlegroups.com.
To view this discussion visit 
https://groups.google.com/d/msgid/php-fig/308cf20d-bdc4-4ae4-b33d-e3367ad4c34a%40app.fastmail.com.
  • Re: Creating a Re... Alex Makarov
  • Re: Creating a Re... Matteo Beccati
    • Re: Creating... 'Andreas Heigl' via PHP Framework Interoperability Group
      • Re: Crea... Matteo Beccati
      • Re: Crea... Ben Ramsey
        • Re: ... Larry Garfield
          • ... Navarr Barnier
            • ... Jaap van Otterdijk
              • ... 'Andreas Heigl' via PHP Framework Interoperability Group
              • ... Larry Garfield
              • ... 'Andreas Heigl' via PHP Framework Interoperability Group
              • ... Larry Garfield
              • ... 'Andreas Heigl' via PHP Framework Interoperability Group
              • ... Korvin Szanto
              • ... 'Andreas Heigl' via PHP Framework Interoperability Group
              • ... Korvin Szanto
              • ... 'Andreas Heigl' via PHP Framework Interoperability Group
              • ... Larry Garfield
              • ... 'Andreas Heigl' via PHP Framework Interoperability Group
        • Re: ... Eric Fortmeyer

Reply via email to