Skip to content

Conversation

@cartermp
Copy link
Contributor

Another round of cleaning upon removing the IVT into FSharp.Editor.

  • Expose a new service for accessing compiler diagnostics
  • Use this service in VS tools that access FSComp instead of FSComp
  • Remove some unused opens

@cartermp cartermp closed this May 30, 2019
@cartermp cartermp reopened this May 30, 2019
@cartermp cartermp closed this May 30, 2019
@cartermp cartermp reopened this May 30, 2019
@cartermp cartermp closed this May 30, 2019
@cartermp cartermp reopened this May 30, 2019
namespace FSharp.Compiler.SourceCodeServices

/// Supported kinds of diagnostics by this service.
type DiagnosticKind =
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cartermp,
Are there other scenarios, where a developer wants to get a string from the compiler.private dll? or are they all diagnostic? Should the Api be named more generaly. Or will the non diagnostic scenarios, expose new modules?

Thanks

kevin

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I imagine I'd have a new ServiceFoo file that services up the Foo stuff from the compiler of the need arises.

@KevinRansom KevinRansom merged commit 9b1287c into dotnet:master Jun 1, 2019
nosami pushed a commit to xamarin/visualfsharp that referenced this pull request Jan 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants