Thread overview
[Issue 20624] [REG2.088] AA access gives wrong deprecation message.
Aug 17, 2021
RazvanN
March 01, 2020
https://issues.dlang.org/show_bug.cgi?id=20624

johanengelen@weka.io changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |industry, rejects-valid
           Priority|P1                          |P5
           Hardware|x86                         |All
                 OS|Mac OS X                    |All
           Severity|enhancement                 |regression

--
July 31, 2020
https://issues.dlang.org/show_bug.cgi?id=20624

johanengelen@weka.io changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P5                          |P1

--
July 31, 2020
https://issues.dlang.org/show_bug.cgi?id=20624

--- Comment #1 from johanengelen@weka.io ---
Instead of opAssign, the better fix is `aa[s] = Nullable!ulong(value);`.

--
August 17, 2021
https://issues.dlang.org/show_bug.cgi?id=20624

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

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

--- Comment #2 from RazvanN <razvan.nitu1305@gmail.com> ---
I cannot reproduce this with latest master. Closing as WORKSFORME. @Johan please reopen if you have anything else to add.

--
August 22, 2021
https://issues.dlang.org/show_bug.cgi?id=20624

--- Comment #3 from johanengelen@weka.io ---
This started working with 2.097. As per the wrong deprecation message, probably this was automatically "fixed" by removing Implicit conversion with alias this.

--