[kprovex] - Allow defining macros in specification module

Open
#2,378 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
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
compilers, tooling

Research direction

Start by tracing kprovex handling of the main module and specification module, especially where syntax productions between them are rejected. Determine whether macro definitions can be supported without repeating the work removed when kprovex was separated. Done means macros can be defined in the specification module with an acceptable overhead cost.

Written by the indexing model from the issue text.

Description

kip

Currently we don't allow any syntax productions between the main module and the specification module.

It would be nice if we could define macros. Not sure what the overhead cost of it would be, if it brings us back to the same state as we were before pulling out kprovex (having to do all the same work again), then it's not worth it.

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.