June 12, 2012 [Issue 5354] formatValue: range templates introduce 3 bugs related to class & struct cases | ||||
---|---|---|---|---|
| ||||
Posted in reply to Denis Derman | http://d.puremagic.com/issues/show_bug.cgi?id=5354 Kenji Hara <k.hara.pg@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #19 from Kenji Hara <k.hara.pg@gmail.com> 2012-06-11 23:40:44 PDT --- Now, various bugs are fixed in std.format module. In class object: - The overridden toString is priority than inherited one. - The overridden toString is priority than user-defined range interface. - The user-defined range interface is priority than inherited toString. In struct object: - User-defined toString is priority than range interface. - If there isn't defined neither toString nor range interface, alias this is considered as proper super type. In all aggregate types: - They can format object lazily with user-specified toString that taking output range. So I close this issue. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- |
Copyright © 1999-2021 by the D Language Foundation