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

Dlang Bot <dlang-bot@dlang.rocks> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |pull

--- Comment #1 from Dlang Bot <dlang-bot@dlang.rocks> ---
@n8sh created dlang/druntime pull request #3034 "`dup`, `idup`, `keys`, `values`: if a type is known to have a postblit do not emit code for the non-postblit path and vice versa" fixing this issue:

- Fix Issue 20741 - `dup`, `idup` for arrays plus `keys`, `values` for built-in associative arrays: if a type is known to have a postblit do not emit code for the non-postblit path and vice versa

https://github.com/dlang/druntime/pull/3034

--

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

Dlang Bot <dlang-bot@dlang.rocks> changed:

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

--- Comment #2 from Dlang Bot <dlang-bot@dlang.rocks> ---
dlang/druntime pull request #3034 "`dup`, `idup`, `keys`, `values`: if a type is known to have a postblit do not emit code for the non-postblit path and vice versa" was merged into master:

- 93bee2277c7c01d92ca6ca55491f8f8c1533664e by Nathan Sashihara:
  Fix Issue 20741 - `dup`, `idup` for arrays plus `keys`, `values` for built-in
associative arrays: if a type is known to have a postblit do not emit code for
the non-postblit path and vice versa

https://github.com/dlang/druntime/pull/3034

--