Skip to content

Conversation

@AdamSpeight2008
Copy link
Contributor

This is an initial implementation of the VB Language Proposal Flags Enum Operators.

 + Added error ERR_MissingFlagsAttributeOnEnum
 + FlagsEnumOperator binder checks to see if member, is an actual member of the Enum referred to.
 + Update nodes.
 + Binds to the enum
 + Flag part binds correct to the actual field in the enum.
 + Attempt at lowering a Flags Enum Expression.
 + Correctly evaluates the FlagsEnumExpression (if you ignore the assert failures)
 + Add the functions that'll do the lowering for FlagSet and FlagClear.
 + Implemented !+ and !- flags enum operator Set and Clear.
 + Classifier (so IDE doesn't crash).
 + Modified the parser so multiple Flags Enum operators can be expressed within a single expression
 + Updated the classification to punctuation.
 + Updated the Lowering to use the correct bound nodes.
 + Implemented Enum Flags Operator !/ (IsAnySet).
 + Extend Enum Flag Operators to use expression after the operator.
Builds OK (except for the following)

...\src\Tools\Source\CompilerGeneratorTools\Source\VisualBasicSyntaxGenerator\VisualBasicSyntaxGenerator.vbproj	1
  The project was restored using Microsoft.NETCore.App version 2.0.7, but with current settings, version 2.0.0 would be used instead.
  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.
  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.

...\src\Tools\Source\CompilerGeneratorTools\Source\BoundTreeGenerator\CompilersBoundTreeGenerator.csproj	1
  The project was restored using Microsoft.NETCore.App version 2.0.7, but with current settings, version 2.0.0 would be used instead.
  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.
  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.

...\src\Tools\Source\CompilerGeneratorTools\Source\CSharpErrorFactsGenerator\CSharpErrorFactsGenerator.csproj	1
  The project was restored using Microsoft.NETCore.App version 2.0.7, but with current settings, version 2.0.0 would be used instead.
  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.
  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.

...\src\Tools\Source\CompilerGeneratorTools\Source\CSharpSyntaxGenerator\CSharpSyntaxGenerator.csproj	1
  The project was restored using Microsoft.NETCore.App version 2.0.7, but with current settings, version 2.0.0 would be used instead.
  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.
  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.

...\src\Tools\Source\CompilerGeneratorTools\Source\VisualBasicErrorFactsGenerator\VisualBasicErrorFactsGenerator.vbproj	1
  The project was restored using Microsoft.NETCore.App version 2.0.7, but with current settings, version 2.0.0 would be used instead.
  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.
  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.
@AdamSpeight2008 AdamSpeight2008 requested review from a team as code owners September 8, 2018 03:33
@jcouv jcouv added PR For Personal Review Only The PR doesn’t require anyone other than the developer to review it. Community The pull request was submitted by a contributor who is not a Microsoft employee. labels Sep 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area-Compilers Community The pull request was submitted by a contributor who is not a Microsoft employee. 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.

3 participants