Definedness conditions for non-total functions in domains.k

Open
#1,223 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Domain
compilers

Research direction

Start by reading domains.k and locating the non-total functions and any existing #Ceil axioms. Define the intended definedness condition for each function in terms of #Ceil axioms, then verify that all listed non-total functions have conditions documenting the cases backend implementers must handle.

Written by the indexing model from the issue text.

Description

Currently there are many non-total functions defined in domains.k.

We should add explicit definedness conditions for each of them (in terms of #Ceil axioms) for two reasons:

  1. Users won't have to add said axioms to their own semantics when doing proofs anymore.
  2. It will show implementers of the backend which cases they are expected to be able to handle.
Dominant language
Python
Stars
591
Forks
163
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from runtimeverification/k

All issues in runtimeverification/k

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.