> break up your big function into small ones. Apart from the obvious maintainability concerns - is there some rule of thumb - how big a function shoul be in order to be inlined either compile time or run time. If a code path is hot - what could stop the inlining? Kind regards: al_shopov
-- 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. For more options, visit https://groups.google.com/d/optout.
