On Jan 5, 2016, at 8:39 AM, Alexander Shopov <a...@kambanaria.org> wrote:
>> 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 In general, I recommend http://docs.racket-lang.org/style/ e.g., http://docs.racket-lang.org/style/Units_of_Code.html#%28part._.Size_.Matters%29 for such things. You really never want to read large units of code, and all software used by someone other than the creator will have to be understood and modified by either an older version of 'you' or someone else. Once you determine that your program is too slow for its intended uses, consider using the Optimization Coach (together with the Profiler) to find out whether a performance-critical part of your code suffers from a lack of in-lining. If, and only if, you know that this is the problem, in-line via suggestions to the compiler or via syntax definitions. -- Matthias p.s. Yes, not all of our software lives up to these standards. No excuses. Occasionally we fail, too. -- 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.
