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
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
gt;> (not demand])
>> (result (demand inputs)
>> (and/c
>> (non-empty-listof (and/c boolean? (curry boolean=? demand)))
>> (compose (curry = (length inputs)) length
>> (map (lambda (s) stars-upon-thars?) sneetches)
Hi!
New to Racket. Looking for expert opinion on my question, but I should give
some background.
I worked on software for about 11 years. Started on Win32 desktop applications
with C++ and then eventually moved to web, where I stayed on front-end
development for about 6 years. Moved to
201 - 204 of 204 matches
Mail list logo