June 13, 2017 Re: dmd: why not use fully qualified names for types in error messages? | ||||
---|---|---|---|---|
| ||||
On Tue, Jun 13, 2017 at 09:50:29PM -0700, Timothee Cour via Digitalmars-d wrote: > eg: > Error: no property 'IF_gray' for type 'ImageFormat' > => > Error: no property 'IF_gray' for type 'foo.bar.ImageFormat' I support such a change. Is there an issue filed in bugzilla for this? I'd add that this would be very useful with Voldemort types, esp. Phobos ones that are generally just named "Result". > and also, why not show where the symbol is defined? Might not be a bad idea, if you're dealing with overloads and don't want to manually scroll through every definition to see which is the relevant one. I'm not 100% sure, but I think this info should already be available in the symbol definition. > would PR's for that be accepted? is that hard to implement? Only Walter / Andrei can answer the first question. For the second question, it doesn't seem hard but it's hard to tell for sure until I look at the actual code. T -- Having a smoking section in a restaurant is like having a peeing section in a swimming pool. -- Edward Burr |
Copyright © 1999-2021 by the D Language Foundation