Thread overview
[Issue 7970] @property does not properly disambiguate delegate properties
Jul 05, 2017
Vladimir Panteleev
Jul 05, 2017
Adam D. Ruppe
Jul 05, 2017
Jonathan M Davis
Jul 07, 2017
Vladimir Panteleev
Jul 07, 2017
Jonathan M Davis
Dec 17, 2022
Iain Buclaw
June 10, 2015
https://issues.dlang.org/show_bug.cgi?id=7970

Andrei Alexandrescu <andrei@erdani.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|unspecified                 |D2

--
July 05, 2017
https://issues.dlang.org/show_bug.cgi?id=7970

Vladimir Panteleev <dlang-bugzilla@thecybershadow.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #1 from Vladimir Panteleev <dlang-bugzilla@thecybershadow.net> ---
-property is gone, so I guess there's nothing to do here...

--
July 05, 2017
https://issues.dlang.org/show_bug.cgi?id=7970

--- Comment #2 from Adam D. Ruppe <destructionator@gmail.com> ---
I actually don't agree this should be wontfix (though that does seem to be the status quo). We don't have -property, but we do still have @property and this is the one compelling case where I actually want to use it.

--
July 05, 2017
https://issues.dlang.org/show_bug.cgi?id=7970

Jonathan M Davis <issues.dlang@jmdavisProg.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |---
           Severity|normal                      |enhancement

--- Comment #3 from Jonathan M Davis <issues.dlang@jmdavisProg.com> ---
(In reply to Adam D. Ruppe from comment #2)
> I actually don't agree this should be wontfix (though that does seem to be the status quo). We don't have -property, but we do still have @property and this is the one compelling case where I actually want to use it.

Agreed. Regardless of -property, without a fix along these lines, the property syntax is somewhat crippled. And @property could still be improved to fix this even if it's unnecessary in most cases that you want to use the property syntax.

I am changing this to an enhancement request though rather than simply reopening it.

--
July 07, 2017
https://issues.dlang.org/show_bug.cgi?id=7970

--- Comment #4 from Vladimir Panteleev <dlang-bugzilla@thecybershadow.net> ---
Wouldn't "fixing" this today be a breaking language change?

As far as I understand, such changes now need to go through the DIP process, though if they're going to break code, that's unlikely to go anywhere.

Does this issue have a snowball's chance in hell to be fixed? If not, then it's pointless to keep it open.

--
July 07, 2017
https://issues.dlang.org/show_bug.cgi?id=7970

--- Comment #5 from Jonathan M Davis <issues.dlang@jmdavisProg.com> ---
(In reply to Vladimir Panteleev from comment #4)
> Wouldn't "fixing" this today be a breaking language change?
> 
> As far as I understand, such changes now need to go through the DIP process, though if they're going to break code, that's unlikely to go anywhere.
> 
> Does this issue have a snowball's chance in hell to be fixed? If not, then it's pointless to keep it open.

It's probably the only thing related to @property that _does_ have a chance of being fixed. It does require a DIP though.

--
December 17, 2022
https://issues.dlang.org/show_bug.cgi?id=7970

Iain Buclaw <ibuclaw@gdcproject.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P2                          |P4

--