Front page | perl.perl5.porters |
Postings from February 2021
This is in reference to github perl issue #18518.
I submitted an rfe to allow ref_to_type's to be used where
ever a specific type was required. This proposal was shut down
without comment or any form of feedback.
This was neither "civil" nor "kind" behavior as required by perl's
SoC (Standards of Conduct). Someone having the power to shutdown
discussions and silence those in the community is a privilege. The
standards of behavior need to be considerably higher for those
who have been granted such privileges.
Not only was this a violation of Perl's SoC, but for it to be someone
invested with privilege was a clear abuse of power. It was not
professional behavior and clearly is evidence that power to silence
others has been handed out too freely.
As was obvious in the discussion -- the ability to substitute
ref_to_type for the same basic, native built-in type was never
tested. Instead, it was conflated with the inclusion of refs to
opaque objects -- which could never work without perl violating the
integrity & assumptions regarding such objects. As far as the
OO methodology is concerned, perl "cannot" modify objects that are
blessed or make any assumptions about them. I put "cannot" in
quotes because as is often stated, perl will often allow things
which you should not do, especially in regards to objects.
Using constructs that override, ignore or force makes the
user of such constructs responsible for resulting problems.
Perl wasn't designed to be a constrictive language, but one
that clearly gives users (and developers) enough rope to
hang themselves.
In the same way privileges on github in the perl project were
given out with the expectation that the people getting such
privileges would be responsible. Someone who abuses such
privileges obviously shouldn't be someone who has such
privileges.
I request that that this issue be put on the inclusion list
for the next public release of perl and that those who have
abused privilege on the website be censured such that such
incidents will not be repeated.
--- original proposal: ----
On making type and ref_to_type equivalent
where ref_to_type is not a legal value.
Make Explicit Sigil and Ref to Same, Equivalent
/(where refs to a type are not legal values)/
*
Wherever the language currently requires a value of type Array or
a value of type Hash will allow a reference to the same type.
*
Any place where the language allows more than one type, will allow
a reference to one of those allowed types.
*Note:* *This feature request excludes indeterminate behaviors.
Thread Next