22 references to Bad
Microsoft.CodeAnalysis.CSharp (22)
Parser\QuickScanner.cs (22)
69(byte)QuickScanState.Bad, // Slash 70(byte)QuickScanState.Bad, // Complex 71(byte)QuickScanState.Bad, // EndOfFile 84(byte)QuickScanState.Bad, // Slash 85(byte)QuickScanState.Bad, // Complex 114(byte)QuickScanState.Bad, // Slash 115(byte)QuickScanState.Bad, // Complex 124(byte)QuickScanState.Bad, // Letter (might be 'e' or 'x' or suffix) 127(byte)QuickScanState.Bad, // Dot (Number is followed by a dot - too complex for us to handle here). 129(byte)QuickScanState.Bad, // Slash 130(byte)QuickScanState.Bad, // Complex 144(byte)QuickScanState.Bad, // Slash 145(byte)QuickScanState.Bad, // Complex 157(byte)QuickScanState.Bad, // Dot (DotDot range token, exit so that we handle it in subsequent scanning code) 159(byte)QuickScanState.Bad, // Slash 160(byte)QuickScanState.Bad, // Complex 171(byte)QuickScanState.Bad, // Punct 173(byte)QuickScanState.Bad, // Compound 174(byte)QuickScanState.Bad, // Slash 175(byte)QuickScanState.Bad, // Complex 231state = QuickScanState.Bad; // ran out of characters in window 235Debug.Assert(state == QuickScanState.Bad || state == QuickScanState.Done, "can only exit with Bad or Done");