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

[rebuttal] add markdown syntax

Browse Source
This commit is contained in:
Ben Greenman 2016-05-04 22:15:56 -04:00
parent 8c74839e0c
commit b42a1af316
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
icfp-2016/rebuttal.txt
View File

@ -39,22 +39,22 @@ Thanks!
functional code can achieve this highly desirable goal. functional code can achieve this highly desirable goal.
================================================================================ ================================================================================
=== END OF FORMAL RESPONSE. Detailed comments to reviewers (RA RB RC) follow. ## END OF FORMAL RESPONSE. Detailed comments to reviewers (RA RB RC) follow.
================================================================================ ================================================================================
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
--- RA RB, re: (printf "~a") #### RA RB, re: `(printf "~a")`
Calling (printf "~a") raises an arity error in our implementation because Calling `(printf "~a")` raises an arity error in our implementation because
"~a" is a valid format specifier yet `printf` is called with zero additional "~a" is a valid format specifier yet `printf` is called with zero additional
arguments. Calling (printf "~b") would give the same arity error. arguments. Calling `(printf "~b")` would give the same arity error.
These both compile in Typed Racket and fail at runtime. These both compile in Typed Racket and fail at runtime.
But writing (printf "~a") was a typo on our part. We intended to use "~s". But writing `(printf "~a")` was a typo on our part. We intended to use "~s".
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
--- RA RB, re: translating the ideas to Typed Clojure, Scala, and Rust #### RA RB, re: translating the ideas to Typed Clojure, Scala, and Rust
These languages have sufficiently powerful syntax extensions. These languages have sufficiently powerful syntax extensions.
@ -67,7 +67,7 @@ Thanks!
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
--- RA, re: Dialyzer #### RA, re: Dialyzer
The Dialyzer belongs in our discussion of related work. The Dialyzer belongs in our discussion of related work.
Its guarantees match our third requirement for elaborations: Its guarantees match our third requirement for elaborations:
@ -85,14 +85,14 @@ Thanks!
----------------------------------------------------------------------------- -----------------------------------------------------------------------------
--- RA, re: using #false in interpretations #### RA, re: using `#false` in interpretations
This was a careless error on our part. This was a careless error on our part.
We meant to use a unique sentinel value, such as a gensymed symbol. We meant to use a unique sentinel value, such as a gensymed symbol.
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
--- RB, re: "most languages fail at runtime" on printf #### RB, re: "most languages fail at runtime" on printf
gcc does indeed print a warning for invalid and mismatched format specifiers. gcc does indeed print a warning for invalid and mismatched format specifiers.
It also complains when called on non-literal strings. It also complains when called on non-literal strings.
@ -103,7 +103,7 @@ Thanks!
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
--- RC, re: flow of Sec. 3 #### RC, re: flow of Sec. 3
RC writes: RC writes: