Well James, you're in luck.
The short answer is, yes, yes you can. You should check out video at
http://lang.video (you can follow the progress either on the blog, the
twitter feed http://twitter.com/videolang , or on github itself:
https://github.com/videolang/video . Alternatively, you are welc
On Tuesday, August 29, 2017 at 10:42:31 AM UTC-7, Tony Garnock-Jones wrote:
> It'd also be great for Racket in general to have better visibility into
> running programs to see what's going wrong with them in situations like
> this.
I think it's possible to do this with existing features and libr
I have been working through The Racket Graphical Interface Toolkit
documentation to learn GUI programming and I thought I would do a small but
useful project. The idea is to make a simple GUI front end which will
formulate commands for ffmpeg to do various video and audio conversions on
select
`identity` is provided by `racket/function` for just this purpose. But
`values` is also there, and some people use it out of habit/tradition.
Sam
On Tue, Aug 29, 2017 at 2:19 PM, David Storrs wrote:
> Title says it all; can anyone explain?
>
> I get that 'values' is variadic but I don't see the
I believe OP is referring to the paragraph about
play-with-frisky-with-laser being their default style and their sincere
recommendation for Racket code style.
It also seems to be the style that most closely matches core APIs.
On August 29, 2017 at 11:23:51, David Storrs (david.sto...@gmail.com)
On Tue, Aug 29, 2017 at 6:12 AM, Neil Van Dyke wrote:
>
>
> (Of course, other general conventions also have their merits, in various
> languages and environments. For example `FrskyLsr_szGetColor()`. And
> `com.example.FriskyLaser.FriskyLaserPlayBehavior.play` and unqualified
> form `play`. Wh
Title says it all; can anyone explain?
I get that 'values' is variadic but I don't see the issue when you know
that you're dealing with only one value -- e.g. in (map identity '(foo
bar)) In such a case the name 'identity' seems much clearer.
--
You received this message because you are subscri
I would love to see some library provide better abstractions for fairly
common cases of keywords like this, but here is how I might write this:
#lang racket
(require (for-syntax syntax/parse
syntax/define
))
(define-syntax (register-nvim-function! stx)
Thanks, Philip -- I've restarted the server. We need better monitoring
for it, but I don't have the time to fix it at the moment.
It'd also be great for Racket in general to have better visibility into
running programs to see what's going wrong with them in situations like
this.
All I could
It's also worth considering that you can munge the names when you
provide -- and your users can munge them on require.
See filtered-out and filtered-in -- as well as the more commonly used
conveniences built on them, like prefix-{in out}, rename-{in out}, and
so on.
I think sometimes the goodnes
Hello,
I have a working macro written using `syntax-parse`, but it still has
some kinks that need to be worked out. What I want the macro to do is
define a function and as it as input to another function. Example:
(define-nvim-function (foo bar baz) #:name "foo" #:sync #f
(display bar)
On Tue, Aug 29, 2017 at 11:12 AM, Neil Van Dyke
wrote:
>
> (Someday, I will have time to release a package that changes how
> `define-struct`/`struct` identifiers are generated, to use `.` or `:`. To
> at least have the appearance of being more idiomatic, to hint at the
> various other specialne
I recommend trying to develop most non-core Racket modules as if you
might want to share them as small reusable third-party open source
packages in the near future. Which has implications for naming.
For reusable third-party Racket packages, right now, I recommend usually
trying to include th
The style guide Jack mentions is not really about the /library's/ name, but
rather about the data type of the main (usually the first) argument, as
saide. For example you could have a library called `my-wonderful-lib' that
experts `vector-splendify', which takes a vector as its first argument.
On
14 matches
Mail list logo