Thread overview | |||||||
---|---|---|---|---|---|---|---|
|
July 04, 2014 [Issue 8561] Make xtoString, xopCmp and xtoHash detection just as tolerant as xopEquals detection | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=8561 --- Comment #2 from Kenji Hara <k.hara.pg@gmail.com> --- xopCmp case is mostly fixed in issue 10567. For xtoHash case, I opened issue 13045. -- |
July 09, 2014 [Issue 8561] Make xtoString detection just as tolerant as xopEquals, xopCmp and xtoHash detection | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=8561 Kenji Hara <k.hara.pg@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Make xtoString, xopCmp and |Make xtoString detection |xtoHash detection just as |just as tolerant as |tolerant as xopEquals |xopEquals, xopCmp and |detection |xtoHash detection --- Comment #3 from Kenji Hara <k.hara.pg@gmail.com> --- Unlike xopEquals, xopCmp and xtoHash, I think that generating xtoString for every types is not so valuable. -- |
December 17, 2022 [Issue 8561] Make xtoString detection just as tolerant as xopEquals, xopCmp and xtoHash detection | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=8561 Iain Buclaw <ibuclaw@gdcproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 |P4 -- |
Copyright © 1999-2021 by the D Language Foundation