Hi all, I have this little toy project[1] to help me learn the language. I
would like to produce a single portable executable that can be executed without
reliance on racket installation. `raco distribute` does produce a "package"
folder. But for small utility tool like this, I would prefer a
> >
> >> ./q
> > q: expects 1 on the command line, given 0 arguments
> >
> > Best,
> > Shu-Hung
> >
> > On Mon, Feb 20, 2017 at 1:12 PM, lu <luke...@gmail.com> wrote:
> >> Hi all, I have this little toy project[1] to help me learn the
uesday, February 21, 2017 at 11:15:46 AM UTC-8, Ethan Estrada wrote:
> On Monday, February 20, 2017 at 12:33:46 PM UTC-7, lu wrote:
> > In fact, I'm wondering if `raco distribute` or `raco exe` is flexible
> > enough to produce a statically linked executable where all the necessary
>
Awesome. Thanks! Where can I find the documentation for this TR reader syntax?
Why is TR not able to figure out the type for these variables without human
help? Does that mean the implementation of `command-line` is in TR and the
types of those variables are inferred by the type system, or they
Ah I found documentation for `#{ x : ... }` at here[1].
[1]:
https://docs.racket-lang.org/ts-guide/more.html#%28part._.Annotating_.Single_.Variables%29
On Monday, March 6, 2017 at 9:50:39 PM UTC-8, lu wrote:
> Awesome. Thanks! Where can I find the documentation for this TR reader syn
On Tuesday, May 16, 2017 at 12:47:37 AM UTC-7, kay wrote:
> Hi I feel this might be a bug, can anyone confirm or suggest a fix?
>
> Here's a minimal usage of `command-line` form:
>
> ```
> #lang typed/racket
>
> (define *message* : (Parameterof (Listof String)) (make-parameter '()))
> (define
6 matches
Mail list logo