suzanne.soy/trivial
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[icfp] put 'correctness' inside 'solution'

Browse Source
This commit is contained in:
ben 2016-03-05 13:43:04 -05:00
parent 64c83f3178
commit c35e37d9a0
2 changed files with 22 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
icfp-2016/correctness.scrbl
View File

@ -1,14 +0,0 @@
@title{Correctness}
Our implementation of @racket[format] in @todo{figure-ref} exhibits a few desirable properties.
@itemlist[
@item{}
]
Generally speaking these properties are the ``right'' way to judge if a transformation is correct.
Open question: can we design a restricted macro language where every transformation
is statically checked to ensure termination and correctness.

22
icfp-2016/implementation.scrbl
View File

@ -13,3 +13,25 @@
@; We don't re-implement format or regexp,
@; but we do implement + and some vector operations, to go faster
@section{Correctness}
Our implementation of @racket[format] in @todo{figure-ref} exhibits a few desirable properties.
@itemlist[
@item{}
]
Generally speaking these properties are the ``right'' way to judge if a transformation is correct.
Open question: can we design a restricted macro language where every transformation
is statically checked to ensure termination and correctness.
We have argued that our macros help typed programming, but they did so only
by going outside the law of the type checker.