On Sunday, 20 December 2015 at 13:55:53 UTC, Jacob Carlborg wrote:
Well..., TextMate parses the error messages, extracts the file
and line info and turns them to links back to the editor.
Yeah, but that's just looking at the first part of the error
which is basically standard. The parts after
On 2015-12-20 14:34, Adam D. Ruppe wrote:
The beauty of error message improvement is it doesn't break any code...
Well..., TextMate parses the error messages, extracts the file and line
info and turns them to links back to the editor. I'm pretty sure of
editors do the same. Of course, it wou
On Sunday, 20 December 2015 at 11:59:05 UTC, NX wrote:
We should seriously find a way to make them error friendly.
I think this change I'm looking at here would make a huge
difference because then you'd be able to see how close you got to
matching the various overloads. (in my other post, I s
On Friday, 18 December 2015 at 18:55:29 UTC, Adam D. Ruppe wrote:
[...]
The biggest problem is overly templated functions. We should
seriously find a way to make them error friendly. Maybe:
auto find(Range : [InputRange], V)(Range haystack, V needle)
Rather than:
auto find(Range, V)(Range hayst
It seems like a small effort with a big return. I definitely
support this. Nice idea.
On Friday, 18 December 2015 at 18:55:29 UTC, Adam D. Ruppe wrote:
...It could also do:
k.d(1):k.foo(int a, string b)
^^^++
k.d(2):k.foo(string b)
^^
I prefer this way than using colors.
And by the way, this thread should ha
On Saturday, 19 December 2015 at 10:34:40 UTC, Jacob Carlborg
wrote:
Although, the (XML) output should contain the semantic meaning
not how it should be displayed. That is, it should contain
something like int rather than
int.
Right.
So I took a stab at playing with this in dmd... and it ac
On 2015-12-18 19:55, Adam D. Ruppe wrote:
Moreover, I wouldn't mind if the compiler had an error output format
that could spit out xml or something for computer consumption, with the
same level of detail (if not more). If I were overhauling it all, I'd
make all error messages inside the compiler
I really want the compiler to be more specific about what worked
and what didn't in error messages. Check this out.
---
void foo(int a, string b) {}
void foo(string b) {}
void main() {
foo(10.2, "foo");
}
---
k.d(5): Error: None of the overloads of 'foo' are callable using
argument ty
