arrow-kt / arrow-kt/arrow-analysis

Better errors for predicate parsing

Open
#23 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
Kotlin
Stars
30
Forks
3
PR merge metrics
No merged PRs in 30d

Description

Right now every problem in a `pre`, `post`, or `require` block gives the very unhelpful message:

```
could not parse predicate
```

We should give more information about what failed in each case (unsupported operation, reference to a variable which is not argument, and so on).

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the predicate parsing code and the existing "could not parse predicate" message for pre, post, and require blocks. Inspect how unsupported operations and non-argument variable references are handled; done means each failure reports useful information about the specific problem.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
compilers, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.