File: typo-correction-ambiguity.cpp

package info (click to toggle)
llvm-toolchain-11 1%3A11.0.1-2
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 995,808 kB
  • sloc: cpp: 4,767,656; ansic: 760,916; asm: 477,436; python: 170,940; objc: 69,804; lisp: 29,914; sh: 23,855; f90: 18,173; pascal: 7,551; perl: 7,471; ml: 5,603; awk: 3,489; makefile: 2,573; xml: 915; cs: 573; fortran: 503; javascript: 452
file content (29 lines) | stat: -rw-r--r-- 985 bytes parent folder | download | duplicates (19) 
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
28
29
 
// RUN: %clang_cc1 -fsyntax-only -verify %s

// Check the following typo correction behavior in namespaces:
// - no typos are diagnosed when an expression has ambiguous (multiple) corrections
// - proper iteration through multiple potentially ambiguous corrections

namespace AmbiguousCorrection
{
  void method_Bar();
  void method_Foo();
  void method_Zoo();
};

void testAmbiguousNoSuggestions()
{
  AmbiguousCorrection::method_Ace(); // expected-error {{no member named 'method_Ace' in namespace 'AmbiguousCorrection'}}
}

namespace MultipleCorrectionsButNotAmbiguous
{
  int PrefixType_Name(int value);  // expected-note {{'PrefixType_Name' declared here}}
  int PrefixType_MIN();
  int PrefixType_MAX();
};

int testMultipleCorrectionsButNotAmbiguous() {
  int val = MultipleCorrectionsButNotAmbiguous::PrefixType_Enum(0);  // expected-error {{no member named 'PrefixType_Enum' in namespace 'MultipleCorrectionsButNotAmbiguous'; did you mean 'PrefixType_Name'?}}
  return val;
}