[Issue 5354] formatValue: range templates introduce 3 bugs related to class & struct cases

[d-bugmail at puremagic.com]

http://d.puremagic.com/issues/show_bug.cgi?id=5354


Rob Jacques <sandford at jhu.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P2                          |P3
                 CC|                            |sandford at jhu.edu
           Platform|x86                         |All
         OS/Version|Linux                       |All
           Severity|blocker                     |major


--- Comment #11 from Rob Jacques <sandford at jhu.edu> 2010-12-30 12:26:10 PST ---
I've decreased the importance of this as there are work arounds. As for my
thoughts, this bug is causing a major loss of function in my update to
std.variant and is going to cause major issues with any type that defines/needs
a permissive opDispatch. Conceptually, I believe formatValue makes a major
mistake by assuming that just because a type satisfies isRange, that it is, in
fact a range. So I believe that if toString is present, it should take
priority. I don't see a problem with ranges that return their own types (i.e.
trees) or the current method of formating in general. (Note that the patch only
deals with ElementType!T == T and not the toString issue)

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------