Daniel Patterson

I totally understand that this kind of documentation isn't a priority, it's just frustrating because in a lot of ways Empire seems like something that would be great for many...

It seems like it is an interaction between the flash messages and `Dream.get "/**"`. Here is a reproduction, I changed the flash example to: ``` let result request = %...

@mfelleisen it's (by design) not. The application is: https://github.com/dbp/htdp-examplar -- I am taking student submissions, swapping their implementations with reference good/bad ones, putting their implementations into good test suites, etc....

@mikesperber All my uses are actually in the code linked above. You can see, e.g., here: https://github.com/dbp/htdp-examplar/blob/297e0776c25dbd13af8605eb69cd2e799b589c0a/main.rkt#L60 -- I have copied the tests earlier (by initializing, loading the file, and...

@wilbowma The former isn't too big of a deal (as I said, having multiple `define-var` forms should be straightforward). To the latter -- to some extent, the docker infrastructure always...

Okay -- I'll work on a minimal pull request, with the aim of avoiding forks.

Probably it would be good to also support hiding interactions (I just created this as #583); then the print should just show whatever is visible?

Is there already a convention in errors and messages whether the `:` is included when referencing types of blocks? My inclination would be to say `f() where: block` (as you...

While obviously there are more complicated math expressions that it wouldn't catch, I feel like this is most likely to occur _at first_, and so it might be "good enough"...

I could use `ask`, but I really like that `cases` is structural, rather than just a series of boolean expressions (I actually wish we had better errors when cases didn't...