Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Alethe
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Model registry
Analyze
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
veriT
Alethe
Commits
cc46e2aa
Commit
cc46e2aa
authored
10 months ago
by
Haniel Barbosa
Committed by
Hans-Jörg
10 months ago
Browse files
Options
Downloads
Patches
Plain Diff
Apply 1 suggestion(s) to 1 file(s)
Co-authored-by:
Haniel Barbosa
<
hanielbbarbosa@gmail.com
>
parent
63282d17
No related branches found
Branches containing commit
No related tags found
1 merge request
!7
Update forall_inst
Pipeline
#24187
passed
10 months ago
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
spec/changelog.tex
+1
-1
1 addition, 1 deletion
spec/changelog.tex
with
1 addition
and
1 deletion
spec/changelog.tex
+
1
−
1
View file @
cc46e2aa
...
@@ -18,7 +18,7 @@ Breaking changes:
...
@@ -18,7 +18,7 @@ Breaking changes:
be
\texttt
{
(x S) (:= (y S) x)
}
.
be
\texttt
{
(x S) (:= (y S) x)
}
.
\item
The arguments for
\proofRule
{
forall
_
inst
}
have been changed to
\item
The arguments for
\proofRule
{
forall
_
inst
}
have been changed to
no longer take the shape of bindings using
\texttt
{
(:= x c)
}
.
no longer take the shape of bindings using
\texttt
{
(:= x c)
}
.
Instead, the list of instatiation terms must follow the variable order.
Instead, the list of instatiation terms must follow the variable order
and cover all the respective bound variables
.
\end{itemize}
\end{itemize}
\noindent
\noindent
...
...
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