- 21 7月, 2015 16 次提交
-
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
After talking to Jason, we just can't see the need for this. We already throttle producing tags when we receive events. Once we've actually gone and computed tags there's no reason to continue throttling a large amount. We might as well just go and report the new tags.
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
This allows taggers to be somewhat stateful, passing information between ProduceTags calls.
-
由 Cyrus Najmabadi 提交于
Conflicts: src/EditorFeatures/Core/Shared/Tagging/TagSources/ProducerPopulatedTagSource.cs
-
由 Cyrus Najmabadi 提交于
-
由 Andy Gocke 提交于
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
由 Manish Jayaswal 提交于
Update Using Additional Files.md
-
由 Jonathon Marolf 提交于
Updating readme for VS 2015 release
-
由 Jonathon Marolf 提交于
-
由 Dustin Campbell 提交于
Update Completion List API to make it easier to provide custom CompletionItem behavior
-
- 20 7月, 2015 3 次提交
-
-
由 Bart Koelman 提交于
-
由 Charles Stoner 提交于
Disable failing test
-
由 Charles Stoner 提交于
-
- 19 7月, 2015 1 次提交
-
-
由 Cyrus Najmabadi 提交于
-
- 18 7月, 2015 20 次提交
-
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
This saves us having to create many requests to the UI thread to do work.
-
由 Cyrus Najmabadi 提交于
-
由 Tomáš Matoušek 提交于
The value of nil heap handles in EnC deltas should be zero
-
由 Tomas Matousek 提交于
-
由 Andrew Casey 提交于
Make TokenOfStringCached independent of length
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
Don't use 'true' with RemoveTagsThatIntersectEdits if we're not actually tracking text changes. It's a no-op in that case.
-
由 Cyrus Najmabadi 提交于
Conflicts: src/EditorFeatures/Core/Implementation/KeywordHighlighting/HighlighterViewTaggerProvider.cs src/EditorFeatures/Core/Implementation/ReferenceHighlighting/ReferenceHighlightingViewTaggerProvider.cs
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
Use hte existing Data-Source extensibility point for determining what to tag in ReferenceHighlighting.
-
由 Cyrus Najmabadi 提交于
Move ReferenceHighlighting over to using the new built-in caret tracking of the tagger infrastructure.
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
由 Charles Stoner 提交于
Incorporate PR feedback from #3813
-
由 Andrew Casey 提交于
For lengths that are not between 2 and 16 (inclusive) it immediately returned its second argument. For all other cases, it inspected the string. When the second argument was anything other than SyntaxKind.Identifier (in particular, SyntaxKind.XmlNameToken), the two values would not agree and so the output depended on the length of the first (string) argument. For example, passing ("a", SyntaxKind.XmlNameToken) used to return SyntaxKind.XmlNameToken, but passing ("aa", SyntaxKind.XmlNameToken) used to return SyntaxKind.IdentifierToken. Now they both return SyntaxKind.XmlNameToken. The only impact seems to be on parsing error recovery. If this turns out to make the behavior less desirable, then then we should change the behavior so that *both* return SyntaxKind.IdentifierToken.
-