Here it is.
https://github.com/racket/racket/blob/master/pkgs/racket-doc/scribblings/reference/stx-trans.scrbl#L31

I agree that it will be good to have a pointer or an example involving
set!-values in the documentation of make-set!-transformer. The status
quo is kind of indirect. The documentation of set!-values explains
that set!-values is expanded into let-values plus set!, and the reader
has to connect the two in order to infer the applicability of
set!-transformers to set!-values forms.

https://docs.racket-lang.org/reference/set_.html#%28form._%28%28lib._racket%2Fprivate%2Fmore-scheme..rkt%29._set%21-values%29%29

On Wed, Jun 24, 2020 at 7:09 PM Jos Koot <jos.k...@gmail.com> wrote:
>
> The docs on make-set!-transformer do not mention that it also applies to 
> set!-values.
>
> That is does apply to both is a good case, I think. I have tried to find the 
> documentation  on the GitHub of racket but could not find it. Please give me 
> a hint where to look, so I can do a pull request for submitting a suggestion 
> of improvement. That is, if such an improvement is wanted, of course. I often 
> have trouble to find docs  code on Racket’s GitHub.
>
> If my suggestion is welcome I am willing to do the job by myself! Just as to 
> be a tiny contributor by myself.
>
> Jos
>
>
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to racket-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/racket-users/5ef3eb1e.1c69fb81.c3c6e.5819%40mx.google.com.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/racket-users/CAMTzy%2BYeASRxnGiv6zQG%3DA6%2B3Og%2BiL7AUc%3DU%2Bp074KH5n0ZnpQ%40mail.gmail.com.

Reply via email to