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

[icfp] remove 'free printing' comment

Browse Source
This commit is contained in:
ben 2016-03-16 01:03:52 -04:00
parent d9d8b3e13e
commit 22583f7983
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
icfp-2016/usage.scrbl
View File

@ -94,8 +94,7 @@ Detecting inconsistencies between a format string and its arguments is straightf
if we define an interpretation @racket[fmt->types] @exact|{$\in \interp$}| for if we define an interpretation @racket[fmt->types] @exact|{$\in \interp$}| for
reading types from a format string value. reading types from a format string value.
In Typed Racket this function is rather simple because the most common In Typed Racket this function is rather simple because the most common
directives accept @code{Any} type of value---in a language with uniform syntax, directives accept @code{Any} type of value.
printing comes for free.
@exact|{ @exact|{
\hfill\fbox{\RktMeta{fmt->types} $\in \interp$} \hfill\fbox{\RktMeta{fmt->types} $\in \interp$}
@ -272,7 +271,7 @@ Chisholm v. Georgia, U.S.
Leaving out an argument to @racket[printf] or passing an extra list Leaving out an argument to @racket[printf] or passing an extra list
when calling @racket[map] will raise an arity error during elaboration. when calling @racket[map] will raise an arity error during elaboration.
On the other hand, if we modified @racket[cite] to take a third argument On the other hand, if we modified @racket[cite] to take a third argument
then the above call to @racket[map] would fail to compile. then the above call to @racket[map] would raise a type error.
@; ============================================================================= @; =============================================================================