Regarding #lang racket/koans, I opened
https://github.com/zyrolasting/racket-koans/issues/24 and would appreciate
comments from those more familiar with defining syntaxes if there are rough
edges in this design.
On Sun, Aug 12, 2018 at 10:57 AM Sage Gerard wrote:
> This is great feedback, thank
This is great feedback, thank you both so much! I like using a language for
this approach as the project evolves, and You's feedback is a good stopgap
that does work, and can be applied in-place.
On Sat, Aug 11, 2018 at 1:01 PM Matthew Butterick wrote:
>
> On Aug 11, 2018, at 9:00 AM, Sage
> On Aug 11, 2018, at 9:00 AM, Sage Gerard wrote:
>
> I'm starting to think writing these kind of exercises in a friendly way is
> only possible with macros, but before I go that far, is it possible for me to
> catch a module-level unbound identifier error and print a rackunit failure
>
Would convert-syntax-error and convert-compile-time-error work? Sure
they are macros, but wrapped up in a nice way.
https://docs.racket-lang.org/syntax/macro-testing.html
On Sat, Aug 11, 2018 at 11:00 AM, Sage Gerard wrote:
> Hi all,
>
> Still working the koans project and am hitting a design
Hi all,
Still working the koans project and am hitting a design snag. My expected
UX is that you clone the repo, run racket koans/all.rkt, and then see
nothing but failing unit tests for you to fix. But since some exercises
have unbound module identifiers
5 matches
Mail list logo
