Hey guys, I ran into some issues because my previous patch was lazy. I
was avoiding optimizing ALL calls to runAsync.onSuccess() in
TypeTightener and MethodCallTightener. Turns out that some projects
*depending* on those calls being optimized. So I went back and added a
way to unambiguously
On 2011/06/01 00:10:58, tbroyer wrote:
On 2011/05/31 23:38:17, xtof wrote:
My apologies dropping the response on this thread (I'd missed the
last
question and had assumed this was good to submit).
Also, I didn't realize that I actually need to fetch and submit this
patch
(I'm not part
101 - 102 of 102 matches
Mail list logo
