[Issue 7838] Give some error messages for wrong ranges

2021-03-16 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=7838 RazvanN changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 7838] Give some error messages for wrong ranges

2012-04-06 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=7838 --- Comment #2 from bearophile_h...@eml.cc 2012-04-06 10:09:17 PDT --- (In reply to comment #1) My understanding is that you would usually put a static assert with isInputRange, or a more specific template from std.range immediately after the

[Issue 7838] Give some error messages for wrong ranges

2012-04-06 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=7838 --- Comment #3 from Matt Peterson revcompg...@gmail.com 2012-04-06 10:47:21 PDT --- Yeah, I think the best solution is to add verifyInputRange etc. templates to std.range, where each criteria is checked by a separate static assert. It's just a

[Issue 7838] Give some error messages for wrong ranges

2012-04-06 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=7838 --- Comment #4 from bearophile_h...@eml.cc 2012-04-06 11:06:31 PDT --- (In reply to comment #3) It's just a little ugly because there will end up being nearly duplicate templates for all the different range types. I think putting such test

[Issue 7838] Give some error messages for wrong ranges

2012-04-05 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=7838 Matt Peterson revcompg...@gmail.com changed: What|Removed |Added CC|