https://issues.dlang.org/show_bug.cgi?id=23823

RazvanN <razvan.nitu1305@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |razvan.nitu1305@gmail.com
         Resolution|---                         |DUPLICATE

--- Comment #1 from RazvanN <razvan.nitu1305@gmail.com> ---
I'm not sure (and the spec does not clarify this) if this should warn since you are not effectively using the field, you are just aliasing it. An arguent can be made both ways, but I am inclined to see this as a bug since if you are a library maintainer that uses other libraries and you create an alias to a deprecated symbol, your users will get a deprecation warning pointing to a third library.

Anyway, I see this as duplicate of https://issues.dlang.org/show_bug.cgi?id=23825 .

*** This issue has been marked as a duplicate of issue 23825 ***

--

https://issues.dlang.org/show_bug.cgi?id=23823

--- Comment #2 from elpenguino+D@gmail.com ---
If value1 is instead at module scope, you do get a deprecation warning.

--