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

2012-06-12 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5354 Kenji Hara k.hara...@gmail.com changed: What|Removed |Added Status|ASSIGNED|RESOLVED

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

2011-10-20 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5354 Kenji Hara k.hara...@gmail.com changed: What|Removed |Added Keywords||patch --- Comment #18

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

2011-01-24 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5354 --- Comment #16 from Denis Derman denis.s...@gmail.com 2011-01-24 05:40:24 PST --- (In reply to comment #15) This wouldn't work because the dynamic type of the object being formatted can differ from the static type the template was

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

2011-01-24 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5354 --- Comment #17 from Max Samukha samu...@voliacable.com 2011-01-24 06:27:00 PST --- (In reply to comment #16) It is an obvious choice: programmers explicitely define toString (later, writeTo) precisely for that ;-) Denis I agree that

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

2011-01-23 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5354 --- Comment #12 from Andrei Alexandrescu and...@metalanguage.com 2011-01-23 13:28:48 PST --- There are good arguments for going either way wrt the relative priority of toString and range interface. Using toString by default is in a way the

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

2011-01-23 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5354 --- Comment #13 from Denis Derman denis.s...@gmail.com 2011-01-23 14:25:33 PST --- (In reply to comment #12) There are good arguments for going either way wrt the relative priority of toString and range interface. Using toString by

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

2010-12-30 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5354 Andrei Alexandrescu and...@metalanguage.com changed: What|Removed |Added Status|NEW |ASSIGNED

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

2010-12-15 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5354 --- Comment #1 from Denis Derman denis.s...@gmail.com 2010-12-15 01:45:30 PST --- started thread: http://lists.puremagic.com/pipermail/digitalmars-d/2010-December/090043.html I marked the bug(s) with keyword 'spec', as it depends on: how do

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

2010-12-15 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5354 Nick Voronin elfy...@gmail.com changed: What|Removed |Added CC||elfy...@gmail.com ---

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

2010-12-15 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5354 --- Comment #3 from Nick Voronin elfy...@gmail.com 2010-12-15 10:02:09 PST --- Created an attachment (id=849) proposed patch -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail

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

2010-12-15 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5354 --- Comment #4 from Nick Voronin elfy...@gmail.com 2010-12-15 10:03:24 PST --- Created an attachment (id=850) testcase for various types -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving

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

2010-12-15 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5354 --- Comment #5 from Denis Derman denis.s...@gmail.com 2010-12-15 10:45:23 PST --- (In reply to comment #2) My thoughts: 1. Using Range interface for formatting classes and structs is a good thing and should stay. Why? Please criticise

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

2010-12-15 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5354 --- Comment #6 from Nick Voronin elfy...@gmail.com 2010-12-15 11:46:24 PST --- 1. Using Range interface for formatting classes and structs is a good thing and should stay. Why? Please criticise my arguments above, especially: *

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

2010-12-15 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5354 --- Comment #7 from Denis Derman denis.s...@gmail.com 2010-12-15 14:36:42 PST --- (In reply to comment #6) 1. Using Range interface for formatting classes and structs is a good thing and should stay. Why? Please criticise my

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

2010-12-15 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5354 bearophile_h...@eml.cc changed: What|Removed |Added CC||bearophile_h...@eml.cc ---