1. 05 8月, 2016 1 次提交
  2. 21 7月, 2016 2 次提交
  3. 20 7月, 2016 2 次提交
  4. 15 7月, 2016 1 次提交
  5. 13 7月, 2016 1 次提交
    • A
      Implements simple cases of tuple name roundtripping (#12344) · 7bd28046
      Andy Gocke 提交于
      For the most part, this change implements the same encoding
      for tuples that we use for dynamic. This means that interface
      implementations and generic constraints are not covered, but
      base types and type parameters are.
      
      This change also doesn't have full tests for "long" tuples (nested tuple
      transformations) or tuple types that can only be constructed in
      metadata.
      7bd28046
  6. 11 7月, 2016 1 次提交
  7. 24 6月, 2016 1 次提交
  8. 01 6月, 2016 1 次提交
  9. 21 5月, 2016 2 次提交
  10. 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
  11. 01 5月, 2016 1 次提交
    • A
      Tuple and underlying type unification. Part 1. · dad5ac23
      AlekseyTs 提交于
      - Include memebers of underlying type into a set of members returned by
      tuple type symbol. Properties and events are not supported at the moment.
      - Track declaration locations for tuple related symbols.
      - Ensure Rest extensions are tuples.
      dad5ac23
  12. 28 4月, 2016 1 次提交
  13. 22 4月, 2016 1 次提交
  14. 21 4月, 2016 2 次提交
  15. 20 4月, 2016 1 次提交
  16. 16 4月, 2016 1 次提交
  17. 07 4月, 2016 1 次提交
  18. 02 4月, 2016 1 次提交
  19. 30 3月, 2016 1 次提交
  20. 29 3月, 2016 1 次提交
  21. 18 3月, 2016 1 次提交
  22. 17 3月, 2016 2 次提交
  23. 09 3月, 2016 2 次提交
  24. 04 3月, 2016 1 次提交
  25. 03 3月, 2016 1 次提交
  26. 24 2月, 2016 1 次提交
  27. 20 2月, 2016 1 次提交
  28. 19 2月, 2016 1 次提交
  29. 18 2月, 2016 2 次提交
  30. 10 2月, 2016 1 次提交
  31. 26 1月, 2016 1 次提交
  32. 18 12月, 2015 1 次提交
    • M
      Allow analyzers to configure generated code analysis. · f876a57f
      Manish Vasani 提交于
      1. Add a new API: AnalysisContext.ConfigureGeneratedCodeAnalysis(GeneratedCodeAnalysisFlags analysisMode)
      Configures analyzer callbacks + diagnostic reporting for the analyzer. Recommended for analyzer authors to always invoke this API.
      
      2. Analyzer driver uses a heuristic to identify generated code:
        1. Symbols marked with GeneratedCodeAttribute.
        2. Files with specific extensions (see [here](http://source.roslyn.io/Microsoft.CodeAnalysis.Workspaces/R/ef3599fb042e3706.html)).
        3. Files which have a single line comment starting with <auto-generated> at the beginning of a source file.
      
      3. Driver defaults for non-configured analyzers:
        1. Run analysis on generated code: This avoids semantic breaks for analyzers and will be guaranteed to be always enabled in future.
        2. Report all diagnostics on generated code: This will likely be changed to perform some level of default filtering after #3705 is implemented.
      
      Fixes #6998
      f876a57f
  33. 04 11月, 2015 1 次提交