Thanks Sam,

fwiw, I did try it via the expander. Perhaps I did not try it out with
the right examples. Or I gave up too soon.
I guess I need to do it a little bit more methodically.

Thanks for the advice
Hemanth

On Sat, Mar 27, 2021 at 12:04 AM Sam Tobin-Hochstadt
<[email protected]> wrote:
>
> I think the best way to start understanding `for/fold` is to look at
> the steps it takes in the macro stepper. That will give you a sense
> for what intermediate macros are used, and what the shape of the
> resulting code is. Once you understand that for some examples, it will
> probably be easier to read the code in for.rkt.
>
> Sam
>
> On Fri, Mar 26, 2021 at 2:15 PM Hemanth Kapila <[email protected]> wrote:
> >
> > Hi,
> >
> > Apologies if this is wrong mailing list for the question.
> > I am trying to understand how  "for/fold" is implemented and I am finding 
> > it tough to grok for.rkt[1]
> > Can some one kindly provide me with some guidance on how to go about 
> > understanding the code in the collects folder?
> > I imagine this is too vague a request , if not off topic. I am trying to 
> > figure out what racket does when it encounters a `for/fold` in a program.
> >
> >
> > Many thanks,
> > Hemanth
> >
> >
> > 1. 
> > https://github.com/racket/racket/blob/master/racket/collects/racket/private/for.rkt
> >
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "Racket Developers" group.
> > To unsubscribe from this group and stop receiving emails from it, send an 
> > email to [email protected].
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msgid/racket-dev/5a6a734b-29ed-4f62-b7de-911eeac96f3dn%40googlegroups.com.



-- 
I drink I am thunk.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/racket-dev/CANOK7kuOa%3DDQN9d_UUPyT3ett_ytOR9x7m%3D4jwP7N%3Dw-Vp2mSA%40mail.gmail.com.

Reply via email to