You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or 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
Performance benchmarks using GetFileInformationByName
This file contains hidden or 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
This file contains hidden or 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
Evolving ChakraCore on Node.js with rebases instead of merges
The Node.js master branch is constantly evolving. The chakracore-master branch is also evolving, both by fixing breaking changes from master and by landing new things, making it better. The goal of the chakracore-master branch is to produce a set of easy to review commits, that can be used to open a pull request against master.
For the master branch in a given moment (tagged master-DATE), we can create a chakracore-DATE branch that represents the state of ChakraCore on Node for that revision of master. When updating master, the dated chakracore branch should be rebased against the new dated master branch, creating a new dated chakracore branch using a pull request. Updates to ChakraCore and ChakraShim should either replace the commits of the original versions, or, if the update should be separated, have a different pull request. A chakracore-master branch can be created pointing to the most recent version of ChakraCo
This file contains hidden or 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