runtimeverification/vlsm

Use constrained concepts across the codebase

Open

#382 opened on Dec 19, 2023

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Coq (1 fork)auto 404
Proof Engineeringgood first issue

Repository metrics

Stars
 (5 stars)
PR merge metrics
 (PR metrics pending)

Description

This is a follow-up to issue #58

The remaining tasks:

  • refactor the codebase to use constrained_message_prop X instead of can_emit (preloaded_with_all_messages_vlsm X)
  • possibly also introduce definition in_futures_constrained, which would be in_futures of a preloaded vlsm
  • update names of lemmas that were affected by introducing constrained concepts in other places (these were PRs from #358 to #371)
  • review the refactorings from the PRs mentioned above and see whether state (preloaded_with_all_messages_vlsm X) should be updated to just state X in any of these

Contributor guide

Research direction
Tech stack
Domain
Issue type
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Prerequisites
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.