Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Contribute to GitLab
Sign in
Toggle navigation
C
cpdt
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
research
cpdt
Commits
0a12e1a4
Commit
0a12e1a4
authored
Sep 01, 2011
by
Adam Chlipala
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Pass through second half of StackMachine
parent
5a46baf2
Changes
3
Expand all
Show whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
98 additions
and
108 deletions
+98
-108
cpdt.bib
latex/cpdt.bib
+7
-0
Intro.v
src/Intro.v
+1
-1
StackMachine.v
src/StackMachine.v
+90
-107
No files found.
latex/cpdt.bib
View file @
0a12e1a4
...
@@ -129,3 +129,10 @@
...
@@ -129,3 +129,10 @@
volume = {76(2-3)},
volume = {76(2-3)},
year = {1988}
year = {1988}
}
}
@article{GADT,
author = {Hongwei Xi and Chiyan Chen and Gang Chen},
title = {Guarded Recursive Datatype Constructors},
booktitle = {Proceedings of the 30th ACM SIGPLAN Symposium on Principles of Programming Languages},
year = {2003}
}
src/Intro.v
View file @
0a12e1a4
...
@@ -167,7 +167,7 @@ Some readers have suggested that I give multiple recommended reading orders in t
...
@@ -167,7 +167,7 @@ Some readers have suggested that I give multiple recommended reading orders in t
Readers
with
no
prior
Coq
experience
can
ignore
the
preceding
discussion
!
I
hope
that
my
heavy
reliance
on
proof
automation
early
on
will
seem
like
the
most
natural
way
to
go
,
such
that
you
may
wonder
why
others
are
spending
so
much
time
entering
sequences
of
proof
steps
manually
.
Readers
with
no
prior
Coq
experience
can
ignore
the
preceding
discussion
!
I
hope
that
my
heavy
reliance
on
proof
automation
early
on
will
seem
like
the
most
natural
way
to
go
,
such
that
you
may
wonder
why
others
are
spending
so
much
time
entering
sequences
of
proof
steps
manually
.
Coq
is
a
very
complex
system
,
with
many
different
commands
driven
more
by
pragmatic
concerns
than
by
any
overarching
aesthetic
principle
.
When
I
use
some
construct
for
the
first
time
,
I
try
to
give
a
one
-
sentence
intuition
for
what
it
accomplishes
,
but
I
leave
the
details
to
the
Coq
reference
manual
%~
\
cite
{
CoqManual
}%.
I
expect
that
readers
interested
in
complete
understandings
will
be
consulting
that
manual
frequently
;
in
that
sense
,
this
book
is
not
meant
to
be
completely
standalone
.
Coq
is
a
very
complex
system
,
with
many
different
commands
driven
more
by
pragmatic
concerns
than
by
any
overarching
aesthetic
principle
.
When
I
use
some
construct
for
the
first
time
,
I
try
to
give
a
one
-
sentence
intuition
for
what
it
accomplishes
,
but
I
leave
the
details
to
the
Coq
reference
manual
%~
\
cite
{
CoqManual
}%.
I
expect
that
readers
interested
in
complete
understandings
will
be
consulting
that
manual
frequently
;
in
that
sense
,
this
book
is
not
meant
to
be
completely
standalone
.
I
often
use
constructs
in
code
snippets
without
first
introducing
them
at
all
,
but
explanations
should
always
follow
in
the
prose
paragraphs
immediately
after
the
offending
snippets
.
*
)
*
)
(
**
**
On
the
Tactic
Library
*
)
(
**
**
On
the
Tactic
Library
*
)
...
...
src/StackMachine.v
View file @
0a12e1a4
This diff is collapsed.
Click to expand it.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment