Skip to content

Better path error reporting #5628

@keyboardDrummer

Description

@keyboardDrummer

Dafny currently may, when postconditions can not be proven, report a specific return location where those could not be proven, in case there are different return locations. However, this does not always work reliably, like here, where we would hope the error is shown in the then branch of the if:

image

In other cases, the error only occurs for a specific path, but for all return locations, like here:

image

So Dafny will not indicate a useful path location by design.

A better UX might be that if only particular branches lead to the exception, that Dafny would tag these branches as related locations.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: error-reportingClarity of the error reportingkind: enhancementEnhancements, feature requests, etc. These are NOT bugs, but ways we can improve Dafnypart: verifierTranslation from Dafny to Boogie (translator)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions