1. 28 7月, 2018 1 次提交
  2. 22 7月, 2018 1 次提交
  3. 13 7月, 2018 1 次提交
  4. 29 6月, 2018 1 次提交
  5. 28 6月, 2018 1 次提交
  6. 24 2月, 2018 1 次提交
    • O
      Support unmanaged constraint (#24817) · eabb4a09
      Omar Tawfik 提交于
      * Source changes for unmanaged (PROTOTYPE for metadata)
      
      * Modreqs for unmanaged as well
      
      * Finished roundtripping metadata
      
      * Added more tests
      
      * Fix CI
      
      * More tests
      
      * Clean up
      eabb4a09
  7. 22 12月, 2017 1 次提交
    • A
      Remove obsolete duplicate APIs from type symbols. (#23888) · 132b91d1
      AlekseyTs 提交于
      This change removes the following APIs:
      - TypeSymbol.BaseType
      - TypeSymbol.Interfaces
      - TypeSymbol.AllInterfaces
      - NamedTypeSymbol.TypeArguments
      - TypeParameterSymbol.ConstraintTypes
      
      These APIs simply delegate the work to APIs with "NoUseSiteDiagnostics" suffix and are not supposed to be used inside compilers. They were left in the code-base because they used to be part of the public surface and the names were nicer, but they are no longer part of the public surface.
      132b91d1
  8. 20 9月, 2017 1 次提交
  9. 25 7月, 2017 1 次提交
  10. 12 7月, 2017 1 次提交
  11. 23 5月, 2017 1 次提交
  12. 19 5月, 2017 1 次提交
  13. 13 4月, 2017 1 次提交
  14. 25 1月, 2017 1 次提交
    • A
      Disallow attributes in local function definitions (#16498) · 81a092b6
      Andy Gocke 提交于
      Attributes will not be permitted on type parameters or parameters of
      local functions. This matches the existing behavior for the return type
      and symbol itself, neither of which allow attributes to be applied to
      them.
      
      Fixes #1640
      81a092b6
  15. 02 8月, 2016 1 次提交
  16. 05 2月, 2016 1 次提交
  17. 11 1月, 2016 1 次提交
    • A
      Round-trip notion of nullable reference types through metadata emit/metadata import cycle. · 7d2e0793
      AlekseyTs 提交于
      Apply NullableAttribute to a module if it utilizes Nullable Reference Types feature.
      Apply NullableAttribute to other targets in the module to point to nullable reference types in type references. The attribute is applied in the same fashion as DynamicAttribute, with the following exceptions:
      - For types of events, it is applied to event declarations (not just to parameters of accessors).
      - Types used as custom modifiers, do not have dedicated transform flags.
      
      Here is the definition of the NullableAttribute required for the successful compilation/metadata import :
      ////
      namespace System.Runtime.CompilerServices
      {
          [AttributeUsage(AttributeTargets.Event | // The type of the event is nullable, or has a nullable reference type as one of its constituents
                          AttributeTargets.Field | // The type of the field is a nullable reference type, or has a nullable reference type as one of its constituents
                          AttributeTargets.GenericParameter | // The generic parameter is a nullable reference type
                          AttributeTargets.Module | // Nullable reference types in this module are annotated by means of NullableAttribute applied to other targets in it
                          AttributeTargets.Parameter | // The type of the parameter is a nullable reference type, or has a nullable reference type as one of its constituents
                          AttributeTargets.ReturnValue, // The return type is a nullable reference type, or has a nullable reference type as one of its constituents
                         AllowMultiple = false)]
          public class NullableAttribute : Attribute
          {
              public NullableAttribute() { }
              public NullableAttribute(bool[] transformFlags)
              {
              }
          }
      }
      ////
      7d2e0793
  18. 04 12月, 2015 1 次提交
    • A
      Initial support for nullable flow analysis in lambdas. · 3deab5fe
      AlekseyTs 提交于
      At the moment we just follow the definite assignment logic. The majority of the work is to make sure proper flow of nullable annotations from target delegate types to lambdas and to make lambda binding caches aware of the annotations.
      3deab5fe
  19. 31 10月, 2015 1 次提交
  20. 16 10月, 2015 1 次提交
  21. 08 9月, 2015 1 次提交
  22. 15 7月, 2015 1 次提交
  23. 15 1月, 2015 1 次提交
  24. 14 1月, 2015 2 次提交
  25. 04 12月, 2014 1 次提交
  26. 20 6月, 2014 1 次提交
    • T
      Splits Microsoft.CodeAnalysis, Microsoft.CodeAnalysis.CSharp and... · fc3b332f
      TomasMatousek 提交于
      Splits Microsoft.CodeAnalysis, Microsoft.CodeAnalysis.CSharp and Microsoft.CodeAnalysis.VisualBasic into portable and desktop assemblies.
      
      Existing Core\Source, CSharp\Source and VisualBasic\Source directories are renamed to Core\Portable, CSharp\Portable and VisualBasic\Portable.
      New sibling Desktop folders are added and non-portable source is moved there.
      "System.Runtime" references has to be removed in order for the portable project system magic to automatically add facade references.
       (changeset 1281686)
      fc3b332f
  27. 19 3月, 2014 1 次提交