Skip to content

Better error messages for templates #1104

@chuggafan

Description

@chuggafan

#1066 reminded me that we have no way to say "We have checked X candidate, Y reason is why this candidate failed" in template instantiations. https://godbolt.org/z/Wa5sPPd5T

Something like that would be extremely helpful in determining for any end user (and us debugging the compiler) what issues the compiler is having during an expansion of a template, the age-old meme of template errors turning into multi-page barf that cannot be understood are true and we should work to avoid continuing it.

This is low on my priority list as I have an existing "Why is omake behaving like this" headache that I shall need to sort out.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions