1. 04 6月, 2020 1 次提交
    • J
      Move the Quick Info handling for await back into Quick Info · a4fb66a3
      Jason Malinowski 提交于
      The Quick Info service mostly defers to the symbol description service
      to do most of it's work; the symbol description service takes a symbol
      and a SemanticModel + position to build up the description of the
      symbol, using that position for minimally qualifying types in some
      cases. This position was also being used by the symbol description
      service to see if the original invocation point was an await, and if so
      it switched to special behavior to give a different message entirely;
      there was some logic in Quick Info itself to also accomodate that.
      
      This moves that special handling back up to Quick Info, and also does
      a bit of a refactoring to include all of the decisions for what Quick
      Info will show into a struct. This will be used later to help the LSIF
      tool because it means if the two structs are equal than we know the
      two Quick Info contents would the same and we can reuse it.
      a4fb66a3
  2. 02 6月, 2020 3 次提交
  3. 01 6月, 2020 5 次提交
  4. 31 5月, 2020 6 次提交
  5. 30 5月, 2020 25 次提交