UnitTestBot / UnitTestBot/ksmt
Value classes instead of Longs in Z3 API
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 42
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Currently, we use long to represent all Z3 native objects: sorts, expressions, declarations.
Also, all Z3.Native methods accept raw longs without any clarification whether it is sort, expr, or whatever else.
The idea is to provide wrappers for Z3.native methods with different value classes for different object kinds.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the Z3.Native methods and how native objects such as sorts, expressions, and declarations are represented throughout the Kotlin API. Identify the distinct object kinds and the methods that accept raw longs. Done means the API uses value classes that distinguish these native objects instead of ambiguous longs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100