Re: [racket-users] Racket koans module language bug

2018-09-02 Thread Sage Gerard
Hi Matthew, Phillip, Forgive the delayed response. I'm better positioned to resume my study on this, and I did not want to close this thread without the thanks that you deserve. Both solutions shine in their own way. Phillip's casework has been exceptionally helpful in shaping thoughts for a more

Re: [racket-users] Racket koans module language bug

2018-08-26 Thread Matthew Butterick
> On Aug 26, 2018, at 5:15 PM, Sage Gerard wrote: > > The intent is to reject code with blanks, and to treat code without blanks as > Racket code that still might not compile There's more than one way to go about it, of course. It could be simpler to make a wrapper around the usual `read-syn

Re: [racket-users] Racket koans module language bug

2018-08-26 Thread Philip McGrath
Thanks for the link to the GitHub repo; that makes it more clear what you want to do. I think, with your proposed `koan` form, you don't necessarily even need a custom #lang, let along a custom reader: `koan` and `_` can be macros that work together, provided by a normal library. Here's a litt

Re: [racket-users] Racket koans module language bug

2018-08-26 Thread Sage Gerard
Hi Phillip, thanks for the quick and detailed reply. Context @ zyrolasting/racket-koans#24 , except WIP implementation does not provide (koan) form. Re: convert-compile-time-error, that traces back to 2.ii. in that issue and You's suggestion i

Re: [racket-users] Racket koans module language bug

2018-08-26 Thread Philip McGrath
In Racket 7, at least, the first error I get is: has-blanks: arity mismatch; the expected number of arguments does not match the given number expected: 0 given: 1 After fixing that, it looks like, in your `read-syntax`, the `with-handlers` form catching `has-blanks?` emits a `module` form wit

[racket-users] Racket koans module language bug

2018-08-26 Thread Sage Gerard
Hello all, First crack at a module language and stuck on a "expected only a `module' declaration; found an extra form" error. This is not a duplicate of this question since the error is slightly different and the error reproduces in the REPL. Here's m