Matthew Flatt

Yet more: Like `$()`, the syntax class ``` syntax_class AGroup: kind: ~group | '$a ...' ``` currently can match 0 terms, which is not like a `Group` match. So far,...

Disallowing a nonempty match to `~group` seems like the right thing and fixes several inconsistencies. It is not completely backward-compatible, and I had to fix a few places in existing...

Related commit: 7d5be7efd0a1e5f6dbe6e19149c6e6893204949f

I can see how this would be useful. The shorthand doesn't quite feel worthwhile to me, but I have no technical objection, and I'm willing to be overridden or outvoted....

At the Racket level, you could use ``` (module-declared? 'rhombus #t) ; loads the module declaration (module->exports 'rhombus) ``` Or you might want `'rhombus/and_meta`, or you might want `'rhombus/meta` separately.

@jsmaniac Overall, I think you must have in mind some situation or constraints where installation and the `raco pkg` tools don't "just work". Maybe we can better understand the problems...

Running `raco setup` after a snapshot upgrade does make sense. That's because all snapshots are configured with the same name, "snapshot", instead of getting a version-specific name. It has never...

There's at least one precedent for removing Y when chaperoning X: `chaperone-evt` turns various things (ports, channels, etc.) into just evts. But I think mostly keeping Y is more common....

I think this needs to be updated for a change to `define-deprecated-alias`, which now requires that `racketblock` is defined before `schemeblock` is defined as an alias, for example.

You could use `syntax-local-lift-module-end-declaration` when expanding within a module (i.e., when `syntax-transforming-module-expression?` returns true).