File: typo-correction-ambiguity.c

package info (click to toggle)
swiftlang 6.1.3-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 2,791,604 kB
  • sloc: cpp: 9,901,740; ansic: 2,201,431; asm: 1,091,827; python: 308,252; objc: 82,166; f90: 80,126; lisp: 38,358; pascal: 25,559; sh: 20,429; ml: 5,058; perl: 4,745; makefile: 4,484; awk: 3,535; javascript: 3,018; xml: 918; fortran: 664; cs: 573; ruby: 396
file content (27 lines) | stat: -rw-r--r-- 721 bytes parent folder | download | duplicates (16) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
 
// RUN: %clang_cc1 -fsyntax-only -verify %s

// Check the following typo correction behavior in C:
// - no typos are diagnosed when a call expression has ambiguous (multiple) corrections

int v_63;

void v_2_0(int v_452, int v_454) {}

int v_3_0(void) {
   for (int v_345 = 0 ; v_63;)
       v_2_0(v_195,  // expected-error {{use of undeclared identifier 'v_195'}}
             v_231);  // expected-error {{use of undeclared identifier 'v_231'}}
}

// Test: no typo-correction diagnostics are emitted for ambiguous typos.
struct a {
  int xxx;
};

int g_107;
int g_108;
int g_109;

struct a g_999;
struct a g_998;
void PR50797(void) { (g_910.xxx = g_910.xxx); } //expected-error 2{{use of undeclared identifier 'g_910'}}