Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
RefinedC
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Iris
RefinedC
Commits
c4ece0aa
Commit
c4ece0aa
authored
4 years ago
by
Michael Sammler
Browse files
Options
Downloads
Patches
Plain Diff
start with GUIDE
parent
ef26b9b0
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
GUIDE.md
+20
-0
20 additions, 0 deletions
GUIDE.md
with
20 additions
and
0 deletions
GUIDE.md
0 → 100644
+
20
−
0
View file @
c4ece0aa
# WIP: Guide for RefinedC developers
This guide has two parts: First, a guide for writing typing rules.
Second, a style guide for RefinedC development.
## Rule guide
1.
`SimplifyHyp`
and
`SimplifyGoal`
rules should match: The
information learned by the
`SimplifyHyp`
rule should be enough to
prove the
`SimplifyGoal`
. Said another way, applying the
`SimplifyHyp`
instance and then proving
`SimplifyGoal`
should be
equivalent to not using any of the two (except for learning more
information).
## Style guide
1.
Follow the std++/Iris style.
2.
If there is a typeclass to restrict when a typing rule applies, but
it does not contain useful information for proving the typing rule,
it should only be on the instance, not the lemma.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment