- 25 10月, 2016 9 次提交
-
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
- 24 10月, 2016 9 次提交
-
-
由 CyrusNajmabadi 提交于
Move PatternMatching over to using immutablearrays.
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
- 22 10月, 2016 9 次提交
-
-
由 Jared Parsons 提交于
Fix build race condition
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
TLDR: artifacts are going to move around in Binaries\Debug and the directory is going to get a lot bigger. At a high level build projects can be classified into three categories based on how they write output: - incorrect: a given output path is written to more than once with different contents - less correct: a given output path is written to more than once but always with the same content - correct: a given output path is written to exactly once Today the roslyn build is decidedly “incorrect” as pretty much every file is written directly into Binaries\Debug. This means it ends up writing pretty much every Visual Studio SDK DLL twice: once for Dev14 and once for Dev15. For example at various points in the build Binaries\Debug\Microsoft.VisualStudio.Text.Data.dll may refer to Dev14 and at others it’s Dev15. If this seems like a scary proposition for a build that’s because it is indeed scary and it has real consequences. By now pretty much everyone on the team has hit the build race condition that is dragging down our PRs. The general fix here is to move build outputs into separate directories. Instead of building to $(Configuration) projects now build into say $(Configuration)\Exes\$(MSBuildProjectFileName). This will have a substantial increase in the size of Binaries. We will be looking into ways to reduce that. In the short term though build stability far outweighs the size increase. This change takes us most of the way to "correct". There are several places I had to compromise in order to get this initial change in: - UnitTests still build to a common output folder (one for Dev14, another for Dev15). Pulling unit tests apart is going to take a bit of work. - Every project has a <RoslynProjectType> entry. This will go away in the future for most projects. It's temporarily needed so I can fix roslyn-internal in parallel without taking down the build. - VSL.Imports.targets is messy. Unavoidable for now due to the above. It will get cleaner as I iterate on this. None of these are relevant to the underlying race condition. Hence it's okay to push them off.
-
由 CyrusNajmabadi 提交于
Keep doc comments at top of file when adding usings.
-
由 CyrusNajmabadi 提交于
-
由 Ravi Chande 提交于
Suggest types (and intrinsic type keywords) after "(" when declaring …
-
由 AlekseyTs 提交于
Remove obsolete code.
-
由 AlekseyTs 提交于
Add dedicated tests for type argument inference from out variable declarations.
-
- 21 10月, 2016 10 次提交
-
-
由 CyrusNajmabadi 提交于
Small rename to help unblock https://github.com/dotnet/roslyn/pull/14577
-
-
由 CyrusNajmabadi 提交于
Remove uncalled method.
-
由 CyrusNajmabadi 提交于
-
由 Heejae Chang 提交于
fixed 2 issue where IDE analyzer throws null exception and host analy…
-
由 AlekseyTs 提交于
The code is related to the feature of supporting explicit parameter-less constructors in structures, which was removed. Also, the code in IsDefaultValueTypeConstructor helper wasn't properly handling constructed or retargeted symbols. Fixes #14541.
-
由 Ravi Chande 提交于
-
由 AlekseyTs 提交于
-
由 Fred Silberberg 提交于
Skip flaky SolutionTests.TestRecoverableSyntaxTreeVisualBasic until …
-
由 Fredric Silberberg 提交于
-
- 20 10月, 2016 3 次提交
-
-
由 Heejae Chang 提交于
fixed 2 issue where IDE analyzer throws null exception and host analyzer exception message not going away from error list issue.
-
由 Heejae Chang 提交于
implements IProjectCacheHostService in OOP.
-
由 Heejae Chang 提交于
workspace will cache everything in memory if this service doesn't exist in workspace. now this being exist, workspace will start to put things such as text, tree, compilation either kick out from memory or save it to temporary storage. this should reduce memory foot print once things become idle, but this doesn't help memory footprint while feature is running. with this service, once OOP become idle, memory foot print goes down to about 700MB to 1 GB. but still while code lens run, memory goes up to 3GB.
-