Breakpoint set on a very different line

[vasily-kirichenko]

I think it's a new level of breakpoints weirdness:

15.5 pre 3

[vasily-kirichenko]

Or try to debug shouldProvideCompletion function. Good luck :)

let shouldProvideCompletion (documentId: DocumentId, filePath: string, defines: string list, text: SourceText, position: int) : bool =
        let textLines = text.Lines
        let triggerLine = textLines.GetLineFromPosition position
        let colorizationData = Tokenizer.getColorizationData(documentId, text, triggerLine.Span, Some filePath, defines, CancellationToken.None)
        colorizationData.Count = 0 || // we should provide completion at the start of empty line, where there are no tokens at all
        colorizationData.Exists (fun classifiedSpan -> 
            classifiedSpan.TextSpan.IntersectsWith position &&
            (
                match classifiedSpan.ClassificationType with
                | ClassificationTypeNames.Comment
                | ClassificationTypeNames.StringLiteral
                | ClassificationTypeNames.ExcludedCode
                | ClassificationTypeNames.NumericLiteral
                | ClassificationTypeNames.VerbatimStringLiteral
                | ClassificationTypeNames.Text -> false
                | _ -> true // anything else is a valid classification type
            ))

There is absolutely no way to set a breakpoint so that colorizationData value can be inspected.

[dsyme]

Interesting, must be in our handling of a || b and a && b. We should at least be committing a breakpoint before the start of these constructs

[vasily-kirichenko]

It jumps to another method. This is something new.

[dsyme]

@vasily-kirichenko Yes indeed

[dsyme]

This is covered by #11980