23 references to Bad
Microsoft.CodeAnalysis.CSharp (23)
Parser\QuickScanner.cs (23)
66(byte)QuickScanState.Bad, // Slash 67(byte)QuickScanState.Bad, // Complex 68(byte)QuickScanState.Bad, // EndOfFile 81(byte)QuickScanState.Bad, // Slash 82(byte)QuickScanState.Bad, // Complex 111(byte)QuickScanState.Bad, // Slash 112(byte)QuickScanState.Bad, // Complex 121(byte)QuickScanState.Bad, // Letter (might be 'e' or 'x' or suffix) 124(byte)QuickScanState.Bad, // Dot (Number is followed by a dot - too complex for us to handle here). 126(byte)QuickScanState.Bad, // Slash 127(byte)QuickScanState.Bad, // Complex 141(byte)QuickScanState.Bad, // Slash 142(byte)QuickScanState.Bad, // Complex 152(byte)QuickScanState.Bad, // Dot followed by number. Could be a fp `.0` or could be a range + num `..0`. Can't tell here. 154(byte)QuickScanState.Bad, // Dot (DotDot range token, exit so that we handle it in subsequent scanning code) 156(byte)QuickScanState.Bad, // Slash 157(byte)QuickScanState.Bad, // Complex 168(byte)QuickScanState.Bad, // Punct 170(byte)QuickScanState.Bad, // Compound 171(byte)QuickScanState.Bad, // Slash 172(byte)QuickScanState.Bad, // Complex 228state = QuickScanState.Bad; // ran out of characters in window 232Debug.Assert(state == QuickScanState.Bad || state == QuickScanState.Done, "can only exit with Bad or Done");