Krzysztof Kotowicz
Krzysztof Kotowicz
Is there any reason not to merge it? This allows d3 to work on applications that use CSP without `unsafe-eval`, which seems quite beneficial. The less-performant branch is only taken...
This is an ongoing project. There is a build target that one can use without the extension code: `./do.sh build_library`. More documentation, code examples and such are incoming.
_From [[email protected]](https://code.google.com/u/[email protected]/) on July 13, 2014 21:24:41_
_From [[email protected]](https://code.google.com/u/[email protected]/) on July 13, 2014 21:24:41_
_From [[email protected]](https://code.google.com/u/[email protected]/) on July 17, 2014 11:04:14_ And...two preliminary patches to goog.crypt.shaX; somewhat faster according to Closure's benchmarks. (And the initial work for prescheduling.) **Attachment:** [CLOSURE.patches](http://code.google.com/p/end-to-end/issues/detail?id=113#hc2)
_From [[email protected]](https://code.google.com/u/[email protected]/) on July 17, 2014 16:52:13_ **Cc:** [email protected] [email protected]
_From [[email protected]](https://code.google.com/u/[email protected]/) on July 17, 2014 17:03:08_ **Labels:** -Priority-Low Priority-Medium Performance Component-Logic
_From [[email protected]](https://code.google.com/u/[email protected]/) on July 18, 2014 14:04:04_ we are getting the external contribution agreement stuff ready. but this patch seems very useful, thank you very much! :) **Status:** Accepted
_From [[email protected]](https://code.google.com/u/[email protected]/) on July 23, 2014 15:59:01_ **Status:** Started **Owner:** [email protected]
_From [[email protected]](https://code.google.com/u/[email protected]/) on July 24, 2014 00:21:18_ Nice performance improvement! Two questions: 1) Are you going to submit the Closure SHA patches to the Closure project directly, or would you...