Re: [PHP-DEV] Renaming type-hints to something else?

2014-09-21 Thread Thomas Gutbier
Am 20.09.2014 um 15:05 schrieb Levi Morrison: On Fri, Sep 19, 2014 at 7:58 AM, thomas.gutb...@anthrotec.de wrote: What's about Typed Arguments? I am proposing return types which are not arguments, so that would be too narrow. Sorry, I have mistaken that related to the recently discussion

Re: [PHP-DEV] Renaming type-hints to something else?

2014-09-20 Thread Levi Morrison
On Fri, Sep 19, 2014 at 7:58 AM, thomas.gutb...@anthrotec.de wrote: Am 19.09.2014 15:21, schrieb Levi Morrison: Anyone else have an opinion they want to voice on this? What's about Typed Arguments? I am proposing return types which are not arguments, so that would be too narrow. -- PHP

Re: [PHP-DEV] Renaming type-hints to something else?

2014-09-19 Thread Levi Morrison
Anyone else have an opinion they want to voice on this? -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Renaming type-hints to something else?

2014-09-19 Thread thomas . gutbier
Am 19.09.2014 15:21, schrieb Levi Morrison: Anyone else have an opinion they want to voice on this? What's about Typed Arguments? -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Renaming type-hints to something else?

2014-09-17 Thread Stas Malyshev
Hi! The general concept should be called Optional Type Declarations, to replace “Type Hinting. They are type declarations, and they are optional. Thus the name. For the things themselves, they’re just Type Declarations, to replace “Type Hints. So, for example: I'd just call it type

Re: [PHP-DEV] Renaming type-hints to something else?

2014-09-17 Thread Dan Cryer
What do you guys think? Has the ship not already sailed on this one? The php.net web site ( http://php.net/manual/en/language.oop5.typehinting.php), and userland developers, have been calling them type hints for years now, I'd imagine whatever new name comes up will largely be ignored outside

Re: [PHP-DEV] Renaming type-hints to something else?

2014-09-17 Thread Sara Golemon
On Sep 16, 2014, at 8:11, Levi Morrison le...@php.net wrote: Can anyone come up with a better name than `hints`? Maybe `type declarations`? Or should we just stick with `hints`? My general feeling is to leave it alone. I agree that it's a misnomer, but as has been mentioned, it's a well

Re: [PHP-DEV] Renaming type-hints to something else?

2014-09-17 Thread Lester Caine
On 17/09/14 09:46, Sara Golemon wrote: As for Hint versus Declaration/Decl or Annotation or whatever... My second choice (since staying with hint is my first) is probably decl(aration). Despite my HHVM loyalties, I'm not fond of using annotation here anyway. There's a reasonable argument

Re: AW: [PHP-DEV] Renaming type-hints to something else?

2014-09-17 Thread Rowan Collins
Robert Stoll wrote (on 16/09/2014): I would argue type declaration is wrong as well since it is not a type declaration as it is known in other languages where the type declaration is binding. IMO it is more a type check. Consider the following function foo(Bar $b){ $b = 1; //$b is not a Bar

AW: AW: [PHP-DEV] Renaming type-hints to something else?

2014-09-17 Thread Robert Stoll
-Ursprüngliche Nachricht- Von: Rowan Collins [mailto:rowan.coll...@gmail.com] Gesendet: Mittwoch, 17. September 2014 18:01 An: internals@lists.php.net Betreff: Re: AW: [PHP-DEV] Renaming type-hints to something else? Robert Stoll wrote (on 16/09/2014): I would argue type

Re: [PHP-DEV] Renaming type-hints to something else?

2014-09-17 Thread Rowan Collins
Sara Golemon wrote (on 17/09/2014): My general feeling is to leave it alone. I agree that it's a misnomer, but as has been mentioned, it's a well established misnomer. I don't see a big gain from it apart from academic purity. I guess in that way it's similar to overloading, which has a

[PHP-DEV] Renaming type-hints to something else?

2014-09-16 Thread Levi Morrison
Dear list, I've always been bothered by the fact that we call type declarations 'hints', as if they aren't enforced. They have always been enforced and we don't have an option to turn them off. I'm wondering if we want to move away from that name to something else. I have two RFCs already that

Re: [PHP-DEV] Renaming type-hints to something else?

2014-09-16 Thread Andrea Faulds
Hi! Here are my thoughts. The general concept should be called Optional Type Declarations, to replace “Type Hinting. They are type declarations, and they are optional. Thus the name. For the things themselves, they’re just Type Declarations, to replace “Type Hints. So, for example: “I am a

Re: [PHP-DEV] Renaming type-hints to something else?

2014-09-16 Thread Levi Morrison
On Tue, Sep 16, 2014 at 9:16 AM, Andrea Faulds a...@ajf.me wrote: Hi! Here are my thoughts. The general concept should be called Optional Type Declarations, to replace “Type Hinting. They are type declarations, and they are optional. Thus the name. For the things themselves, they’re just

Re: [PHP-DEV] Renaming type-hints to something else?

2014-09-16 Thread Andrea Faulds
On 16 Sep 2014, at 16:24, Levi Morrison le...@php.net wrote: On Tue, Sep 16, 2014 at 9:16 AM, Andrea Faulds a...@ajf.me wrote: The general concept should be called Optional Type Declarations, to replace “Type Hinting. They are type declarations, and they are optional. Thus the name. For

AW: [PHP-DEV] Renaming type-hints to something else?

2014-09-16 Thread Robert Stoll
-Ursprüngliche Nachricht- Von: Andrea Faulds [mailto:a...@ajf.me] Gesendet: Dienstag, 16. September 2014 17:26 An: Levi Morrison Cc: internals Betreff: Re: [PHP-DEV] Renaming type-hints to something else? On 16 Sep 2014, at 16:24, Levi Morrison le...@php.net wrote: On Tue