FStarLang / FStarLang/FStar

Generating `triples` and `unconditional` form for a DM4F effect

Open
#758 0 comments 0 reactions 0 assignees View on GitHub
component/dm4free kind/enhancement
Dominant language
F*
Stars
3.1k
Forks
267
Avg merge
10h 45m
Merged PRs (30d)
54

Description

It would not be really difficult to have FStar generate for each DM4F effect MYEFFECT an effect
````
effect MyEffectTriple (a:Type) (pre: MYEFFECT.pre) (post: MYEFFECT.post a) =
MYEFFECT a (fun x1 .. xn p -> pre x1 ... xn /\
(forall y1 .. ym . pre x1 ... xn /\ post y1 ... ym ==> p y1 ... ym))
````

as well as

````
effect MyEffectNull (a:Type) =
MYEFFECT a MYEFFECT.null_wp
````

The main "technical problem" to solve is how we give access to them after generation. Should we declare
new effects MYEFFECTTRIPLE and MYEFFECTNULL, or should we access them through MYEFFECT.Null/MYEFFECT.Triple (one caveat of this last approach is that MYEFFECT is not a namespace...)

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the DM4F effect-generation path and the MYEFFECT, MYEFFECT.pre, MYEFFECT.post, and MYEFFECT.null_wp definitions named in the issue. Determine how generated MyEffectTriple and MyEffectNull effects should be exposed, then verify that generation produces both forms with the intended access convention.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.