1. 26 7月, 2019 1 次提交
  2. 25 7月, 2019 1 次提交
  3. 17 7月, 2019 1 次提交
  4. 12 7月, 2019 1 次提交
  5. 15 3月, 2019 1 次提交
  6. 12 3月, 2019 1 次提交
  7. 21 2月, 2019 1 次提交
  8. 30 1月, 2019 1 次提交
  9. 21 12月, 2018 1 次提交
  10. 11 5月, 2018 1 次提交
  11. 31 1月, 2018 1 次提交
  12. 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
  13. 17 6月, 2017 1 次提交
  14. 19 5月, 2017 1 次提交
    • O
      Generate readonlyattribute if it does not exist (#18715) · d63f0384
      Omar Tawfik 提交于
      * Call this.DeclaringCompilation.EnsureReadOnlyAttributeExists() when needed
      
      * Promote EmbeddedAttribute to be used by both compilers
      
      * Generate Embedded attributes on PE Module Builder
      
      * Thread PEModuleBuilder through Symbol.AddSynthesizedAttributes()
      
      * Fix failing tests
      
      * Base case passing
      
      * Refactor ReadOnlyAttribute to IsReadOnlyAttribute
      
      * Fix build break
      
      * More Tests
      
      * Clean up
      
      * PR Comments #1
      
      PR Comments #3
      
      PR Comments #4
      
      PR Comments #5
      
      PR Comments #6
      
      PR Comments # 7
      
      * Handle NoPIA
      
      Added more tests
      
      * Lambdas and Local functions no longer generate attributes in symbols
      
      Added tests for constructors and operators
      
      Signal need for synthesized attributes in local rewriter for lambdas an local functions
      
      Clean up
      
      * Clean up
      
      * More PR Feedback
      
      * Adding more tests
      
      * More PR Comments
      
      * More tests for explicit interface implementations
      
      * Latest PR Comments
      
      * Moved EnsureIsReadOnlyAttributeExists to AfterAddingTypeMembersChecks
      
      * Fix failing tests
      d63f0384
  15. 10 12月, 2016 1 次提交
  16. 21 11月, 2016 2 次提交
  17. 17 11月, 2016 1 次提交
  18. 04 11月, 2016 1 次提交
  19. 28 9月, 2016 1 次提交
  20. 27 8月, 2016 1 次提交
  21. 05 8月, 2016 1 次提交
  22. 22 7月, 2016 1 次提交
  23. 15 7月, 2016 1 次提交
  24. 14 7月, 2016 1 次提交
  25. 04 5月, 2016 1 次提交
    • A
      Tuple and underlying type unification. Part 2. · ffd32423
      AlekseyTs 提交于
      - Substitute underlying type with corresponding tuple type at the point of type reference.
      - Adjusted implementation of symbol display to account for presence of names in the extension tuples.
      - Implemented proper retargeting for tuple types (multi-targeting support).
      ffd32423
  26. 28 4月, 2016 1 次提交
  27. 16 10月, 2015 1 次提交
  28. 07 10月, 2015 1 次提交
  29. 22 8月, 2015 1 次提交
  30. 17 7月, 2015 1 次提交
  31. 10 6月, 2015 1 次提交
  32. 20 5月, 2015 1 次提交
  33. 11 3月, 2015 1 次提交
  34. 15 1月, 2015 1 次提交
  35. 14 1月, 2015 1 次提交
  36. 29 10月, 2014 2 次提交
    • C
      Correct typos (changeset 1361693) · db63eb4f
      ChuckStoner 提交于
      db63eb4f
    • J
      Create an analyzer to detect verbatim crefs, clean up our codebase to match. · 349040ab
      jasonmalinowski 提交于
      In some parts of our codebase, we use "verbatim crefs" where the compiler just passes the cref name out to the XML file and doesn't do any analysis of it. While there are some legitimate uses of these, there were many abuses in our source code. Worst of all, in some cases we had verbatim crefs on public types that referenced types that had since been renamed, or the syntax was wrong, etc. With this change, there's now an analyzer that issues a warning for all uses of them. In the places that are fair uses of them, the warning is suppressed. Going forward, adding suppressions should be considered fine as long as:
      
      1) it's a reference to something in another layer or language
      2) it's some framework type that's clearly never going to change ever
      
      Otherwise, a proper, verifiable syntax should be used. Again, this isn't to say that verbatim crefs are universally bad, but just that we've proven we make mistakes with them and some guards should be put in place. (changeset 1360175)
      349040ab
  37. 02 7月, 2014 1 次提交
  38. 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