<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 4 Nov, 2017, at 11:43 AM, Peter Ludemann via Python-Dev <<a href="mailto:python-dev@python.org" class="">python-dev@python.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><div class="gmail_default" style="font-family: verdana, sans-serif;"><div class="gmail_default">If type annotations are treated like implicit lambdas, then that's a first step to something similar to Lisp's "special forms". A full generalization of that would allow, for example, logging.debug to not evaluate its args unless debugging is turned on (I use a logging.debug wrapper that allows lambdas as args, and evaluates them if debugging is turned on).</div></div></div></div></blockquote><div><br class=""></div><div>Interestingly enough, at Facebook we found out that using f-strings is *faster* at runtime than the lazy form of logging.log("format with %s and %d", arg1, arg2), including for cases when the log message is not emitted.</div><div><br class=""></div><div>- Ł</div></div></body></html>