jsPerf backend v2.0.0 #1
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 19 commits
February 21, 2015 15:06
| <section id="prep-code"> | ||
| <h2>Preparation code</h2> | ||
| <pre><code><?php | ||
|
|
||
| class Swap { | ||
| public static $items = array(); | ||
|
|
There was a problem hiding this comment.
@mathiasbynens I can't find $scripts defined anywhere for lines 26 and 29 below. safe to delete?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is tracking moving all of the existing backend functionality to jsperf/jsperf.com. My idea is to remove things piece by piece as they are added to the new repo. If (when) anyone else wants to contribute, we'll all know what's left.