New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Safe call is not implemented yet... #16859
Comments
From @KES777Hello Perlbug, Heh... why most wanted feature still is not implemented in perl? https://kotlinlang.org/docs/reference/null-safety.html Probably because someone argue that ~> looks differently on some But most people like it: https://www.perlmonks.org/?node_id=973015 Are there plans to implement it? PS. I post this question to perlbug because this is not the question -- |
From @jkeenanOn Sun, 03 Mar 2019 10:50:47 GMT, kes-kes@yandex.ru wrote:
How does what you are referring to differ from the Postfix Dereference Syntax implemented beginning in perl-5.20? (perldoc perlref) -- |
The RT System itself - Status changed from 'new' to 'open' |
From @GrinnzOn Sun, 03 Mar 2019 07:09:00 -0800, jkeenan wrote:
That is unrelated. This is referring to an operator that would, upon being used to call a method on an undef value, return undef, and otherwise call the method. |
From @GrinnzHere is a previous (extensive) discussion: https://www.nntp.perl.org/group/perl.perl5.porters/2010/11/msg165931.html |
From @jkeenanOn Sun, 03 Mar 2019 18:24:18 GMT, grinnz@gmail.com wrote:
Thanks for the clarification. I should note that the perlmonks thread cited and a P5P thread of around the same time (https://www.nntp.perl.org/group/perl.perl5.porters/2012/05/msg187114.html) petered out with no action being taken. So if we're going to take any action in this regard, we need a fresh statement of the rationale for the operator and a patch implementing it. -- |
This is formalized in RFC 0018, currently awaiting revision, approval and implementation. |
Migrated from rt.perl.org#133877 (status was 'open')
Searchable as RT133877$
The text was updated successfully, but these errors were encountered: