Re^4: Experimental features: autoderef vs postfix deref

Answering for this particular case only, I'd say yes, it's safe. No problems were encountered, and there's no reason to expect that any will. It's an uncontroversial feature whose promotion out of experimental status was unanimous. It will only officially come out of experimental when 5.24 comes out next May-ish, but it's safe bet it will.

Comment on Re^4: Experimental features: autoderef vs postfix deref

Replies are listed 'Best First'.
Re^5: Experimental features: autoderef vs postfix deref by stevieb (Canon) on Jul 13, 2015 at 17:27 UTC
Thank you for this, ikegami, it's what I was hoping to hear. After spending most of the day yesterday learning about the process of how experimental features are implemented, discussed, life cycle etc, I'm confident that `postderef` is one that'll stay around. I think I'll take one of my past modules where there are a lot of circumfix ops, and replace with postderef just to see if the overall readability is improved while scanning a file or not.	[reply] [d/l]

Replies are listed 'Best First'.

Re^5: Experimental features: autoderef vs postfix deref
by stevieb (Canon) on Jul 13, 2015 at 17:27 UTC

Thank you for this, ikegami, it's what I was hoping to hear.

After spending most of the day yesterday learning about the process of how experimental features are implemented, discussed, life cycle etc, I'm confident that postderef is one that'll stay around.

I think I'll take one of my past modules where there are a lot of circumfix ops, and replace with postderef just to see if the overall readability is improved while scanning a file or not.

[reply]
[d/l]