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

Jack Stouffer <jack@jackstouffer.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jack@jackstouffer.com
           Hardware|x86_64                      |All
            Summary|Synchronized class methods  |[REG 2.071] Synchronized
                   |give warnings for RMW       |class methods give warnings
                   |operations                  |for RMW operations
                 OS|Linux                       |All
           Severity|enhancement                 |regression

--

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

anonymous4 <dfj1esp02@sneakemail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|regression                  |enhancement

--- Comment #1 from anonymous4 <dfj1esp02@sneakemail.com> ---
Errm, deprecation is not a regression. Synchronized methods do not provide guarantee of mutually exclusive access. The synchronized method alone does use synchronization, but this tells nothing about other code, which may not use synchronization, also the data accessed is not necessarily unique.

--

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

--- Comment #2 from anonymous4 <dfj1esp02@sneakemail.com> ---
Though it's a good illustration that hand-holding restrictions on shared types make them more painful to use even though people complain that shared is already difficult to use. More ceremony only make situation worse.

--

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

Iain Buclaw <ibuclaw@gdcproject.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|enhancement                 |regression

--

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

Iain Buclaw <ibuclaw@gdcproject.org> changed:

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

--- Comment #3 from Iain Buclaw <ibuclaw@gdcproject.org> ---
Now (correctly) an error since 2.080.1.

--