Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge 'dotnet/master' into DefaultInterfaceImplementation #19648

Conversation

AlekseyTs
Copy link
Contributor

No description provided.

TyOverby and others added 30 commits May 10, 2017 11:22
Fixes dotnet/project-system#2062.

Currently we match a hierarchy node representing an analyzer in Solution Explorer up to the proper Roslyn `AnalyzerReference` based on the "display name"--basically, the name of the assembly without the extension. This mostly works, but you can run into problems if a project uses two different versions of the same analyzer, each with a different set of diagnostics. In this case expanding one of the analyzer nodes in Solution Explorer will show you the wrong set of diagnostics for one or the other, since they both have the same display name.

To uniquely identify an analyzer assembly we should use its full path rather than the display name. However, the project system initially didn't expose the full path through the hierarchy node. This has been fixed, and now the full path is one of the components of the node's "canonical name", along with other bits of information such as the project directory and target framework.

This commit updates our code to extract and use the full path instead of the display name.
Re-enable roslyn analyzers on Roslyn.sln and update public api file f…
CyrusNajmabadi and others added 24 commits May 17, 2017 12:20
Move DocumentHighlights data types down to the 'Features' layer.
Fix bug when caret is at the end of an argument
Enable debug information by default in CSI
…f_empty_for_loops

Issue dotnet#10428: Formatting of empty loops now respects CSharp spacing options
Fix bug when caret is at the end of a numeric literal
LambdaRewriter should only assign proxies from locals in original frame in EE
Reuse local rewriter to derive arguments for IHasArgumentsExpression
The PDB path which is written into the PE file should respect the
`/pathmap` option passed to the compiler.  This is necessary to ensure
that PEs can be deterministic when built from different source paths.

The feature flag `pdb-path-determinism` is being kept for the time
being.  Even though it's a feature flag it still seems inappropriate to
break customers in a point release.  Deferring the removal until the
next major release to give customers time to react.  This issue tracks
removing the flag:

dotnet#19592

closes dotnet#9813
Clarify error message when this is returned by reference
Include overflow checks in tuple conversions
bypass command line argument passing if no command line parser is available
@AlekseyTs AlekseyTs added Area-Compilers Language-C# Feature - Default Interface Impl Default Interface Implementation PR For Personal Review Only The PR doesn’t require anyone other than the developer to review it. labels May 19, 2017
@AlekseyTs AlekseyTs merged commit 0193f8f into dotnet:features/DefaultInterfaceImplementation May 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Compilers cla-already-signed Feature - Default Interface Impl Default Interface Implementation Language-C# PR For Personal Review Only The PR doesn’t require anyone other than the developer to review it.
Projects
None yet
Development

Successfully merging this pull request may close these issues.