Hello,
Please, find below the 1st call for participation for IFL 2018.
Please forward these to anyone you think may be interested.
Apologies for any duplicates you may receive.
best regards,
Jurriaan Hage
Publicity Chair of IFL
---
CALL FOR PARTICIPATION:
The "threading" package is an example of something I'd like to see promoted
to the main Racket distribution.
Reason: it adds clarity for an attractive style, and makes it available
out-of-the-box*, on a par with e.g. Clojure, F#, and Elm.
Just my opinion.
But it does raise a question for the
I was impressed with Lexi's struct-update module and wanted to extend it a
bit, so I've been working on a version of my own that exports a macro
called 'struct++'. I'm having some issues with phase level when applying
contracts to fields.
Here are some examples:
#lang racket
(require struct++)
You're losing the binding information by doing syntax->datum. Here's a
quick change to get you unstuck:
...
(only-in racket/list partition flatten append-map)))
; Include append-map
...
(partition (syntax-parser [(flag _) (syntax-e #'flag)])
Hi,
Racket seems to depricate redefinition of functions at run-time. Since
Racket isn't Scheme, why not prevent that and get back that performance?
-Arthur
==
Arthur Nunes-Harwitt
Computer Science Department, Rochester Institute
I think Racket handles this pretty well. The rule it defines is that a module
cannot directly mutate another module's top-level symbols. This means that if a
module itself does not contain any mutations of a top-level function, that
definition cannot be changed at runtime. Therefore, everyone
6 matches
Mail list logo
