Thread overview |
---|
April 24, 2021 [Issue 21857] TypeInfo_Array.compare can give wrong result when either array exceeds 2GB | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=21857 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 #3450 "TypeInfo_Array.compare can give wrong result when either array exceeds 2GB" fixing this issue: - Fix 21857: TypeInfo_Array.compare can give wrong result when either array exceeds 2GB https://github.com/dlang/druntime/pull/3450 -- |
April 26, 2021 [Issue 21857] TypeInfo_Array.compare can give wrong result when either array exceeds 2GB | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=21857 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 #3450 "TypeInfo_Array.compare can give wrong result when either array exceeds 2GB" was merged into stable: - 93741516a95e8d1a76290c94a7dd9d608d2660b0 by Nathan Sashihara: Fix 21857: TypeInfo_Array.compare can give wrong result when either array exceeds 2GB https://github.com/dlang/druntime/pull/3450 -- |
May 12, 2021 [Issue 21857] TypeInfo_Array.compare can give wrong result when either array exceeds 2GB | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=21857 --- Comment #3 from Dlang Bot <dlang-bot@dlang.rocks> --- dlang/druntime pull request #3468 "merge stable" was merged into master: - e70d111cda2c8009028a985c9ef383b8f759af32 by Nathan Sashihara: Fix 21857: TypeInfo_Array.compare can give wrong result when either array exceeds 2GB https://github.com/dlang/druntime/pull/3468 -- |
Copyright © 1999-2021 by the D Language Foundation