Alex Knauth

Renaming one of the 2 `a` variables to something else also solves this issue, and allows it to run without the `a: undefined; cannot use before initialization` error.

For `any-wrap/c` to avoid wrapping these, I don't see why TR's types not tracking `prop:sealed` should be relevant... `any-wrap/c` can use runtime reflection operations right? The important thing would be...

It seems weird to me that `hash-filter` would work on mutable hashes at all. Where I would think there would be 2 separate operations: `hash-filter` for immutable ones, and `hash-filter!`...

`hash-filter` should not mutate the hash table it's given.

> I don't think that any of match patterns, syntax parse patterns, require forms, or provide forms have local binding forms. (Please correct me if I'm wrong!) All bindings splice...

Your "An example to help consider when use-site scopes are necessary", modified to use `~do`: ```racket (let ([x 'outer]) (define-syntax ~m (pattern-expander (syntax-parser [(_) #'(~do (define-syntax-rule (m arg) (begin (define...

@fare Although https://github.com/Glow-Lang/glow/pull/419 is no longer necessary, I still think `lazy-import` could be a good addition to `gerbil-utils` on its own.

Yes, it's only for functions, inspired by how Racket's `lazy-require` is only for functions. That's documented [here for lazy-require](https://docs.racket-lang.org/reference/lazy-require.html#%28form._%28%28lib._racket%2Flazy-require..rkt%29._lazy-require%29%29): > Defines each `fun-id` as a function that, when called, dynamically...

The inspiration from Racket's `lazy-require` is also the reason for the parentheses being as "heavy" as they are.

Why wouldn't `sequence->list` work? All streams are sequences, right? So `(stream? empty-sequence)` shouldn't be necessary. `(sequence? empty-stream)` would be necessary instead, and that's fine because it's true.