Max Haughton

https://github.com/dlang/DIPs/pull/196 Take a look at this.

> `core.reflect` should actually help with this. I think `core.reflect` would be like using a sledgehammer to pet a dog in this particular usecase (if it could, nice, but writing...

> Here is a snippet from a program I am writing: > > ```d > extern(C++, example) struct AndroidHelloWorld { > mixin AndroidClass!AndroidHelloWorld; > @Import static void sayHello(); > }...

> Because it does not carry context applied element (like which overload, or is the UDA made for class, struct). It does just carry the name of the symbol, which...

Added GSOC '21 since I am available to mentor it

> I would say that this is a rather subjective task. I, for one, prefer DMD's conciseness over what GCC and Rust produce for this specific message. Some other messages...

> @maxhaton I think that the project should simply be to update the error reporting mechanism and later on, on a case by case basis see if we could improve...

> @maxhaton > > > D should provide an annotated quotation of the offending code. > > `dmd -verrors=context` already does this: > > ``` > ../old/sample/enuminit.d(5): Error: cannot implicitly...

It would be good if this ended up with some boilerplate/guidance along the lines of "How to add D support to your toolchain" on our website, thinking about it.

I have just started fiddling around with bolting Z3 onto the dmd-frontend, so it may be possible to attack this area from both sides eventually.