- 27 6月, 2018 1 次提交
-
-
由 Cyrus Najmabadi 提交于
-
- 15 2月, 2018 1 次提交
-
-
由 Cyrus Najmabadi 提交于
Produce warning for VB code. Fix spelling mistake. Add loc files. Fall back to tuples if they're available when making a hashcode. Use System.HashCode if its available. Use 64bit math when computing VB hashcodes in checked contexts. Use full 32 bits for vb hash. Cleanup
-
- 13 7月, 2017 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 17 6月, 2017 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 22 3月, 2017 2 次提交
-
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
- 20 3月, 2017 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 10 3月, 2017 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 23 2月, 2017 2 次提交
-
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
- 10 2月, 2017 3 次提交
-
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
- 20 7月, 2016 2 次提交
-
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
- 16 10月, 2015 1 次提交
-
-
由 Paul Harrington 提交于
-
- 26 8月, 2015 1 次提交
-
-
由 Dustin Campbell 提交于
-
- 01 2月, 2015 1 次提交
-
-
由 beep boop 提交于
Background: As discussed in the dev team all hands all code under the GitHub dotnet foundation is using a single process for contribution, API review, infrastructure and coding style. The idea is to present a unified view to our customer and give them a single story for contributing to any project under the dotnet foundation. https://github.com/dotnet/corefx/wiki/Contributing#c-coding-style The coding style transition is automated using a Roslyn based rewrite tool: https://github.com/dotnet/codeformatter This will be applied in stages across our developer tree. Right now the focus is on the Open directory as this is what is being presented on github. Code owners will be contacted before the transition happens. Note: this is a soft style requirement. There are no build errors that come from this change. (changeset 1408227)
-
- 27 1月, 2015 1 次提交
-
-
由 beep boop 提交于
-