Backend support for modular KORE

Open
#3,948 1 comment 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
Domain
compilers

Research direction

Start by reading definition.kore and the linked prelude.kore file, then examine how the backends consume a KORE definition during kompilation. Determine which backend changes are necessary for modular input definitions; the work is done when the required modular support is implemented and its behavior is verified.

Written by the indexing model from the issue text.

Description

Currently, definition.kore, apart from a static prelude prepended to each KORE definition during kompilation, is basically not modular.

As the first step towards incremental kompilation, investigate what changes are necessary on the backends to support a modular input definition.

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.