On text operator, reported unexpected error

[pointertobios]

Environment

• OS and Version: archlinux
• VS Code Version: 1.95.3
• C/C++ Extension Version: 1.22.11

Bug Summary and Steps to Reproduce

Bug Summary:

inline constexpr unsigned long long operator"" u64(unsigned long long n){return n;}

auto x = 0xfffu64 + 1u64;

reported "Extra text after expected end of number" on 0xfffu64 and 1u64 and consider them as int.

But it can be compiled by g++ and clang++. And there is no limit about number character on the text operator in C++ standard.

Configuration and Logs

none

Other Extensions

No response

Additional context

No response

[sean-mcmanus]

@pointertobios I'm seeing compiler errors with g++/clang++ -- what version are you using and what args like -std=c++20 are you using?

[pointertobios]

@pointertobios I'm seeing compiler errors with g++/clang++ -- what version are you using and what args like -std=c++20 are you using?

@sean-mcmanus yes c++20

[pointertobios]

@pointertobios I'm seeing compiler errors with g++/clang++ -- what version are you using and what args like -std=c++20 are you using?

@sean-mcmanus sorry I just type wrong code.the argument is also unsigned long long in my actually used code.I corrected the example now.

[pointertobios]

[pointertobios]

[pointertobios]

In clang++ add a _ before can be compiled.
But c/c++ extension reported the same error

[Colengms]

Hi @pointertobios . If I add "_", like so:

inline constexpr unsigned long long operator"" _u64(unsigned long long n){return n;}

auto x = 0xfff_u64 + 1_u64;

int main() {
	return 0;
}

... For me, that both allows the code to compile with clang++ and clears up the IntelliSense squiggle. If you're seeing something different, could you provide a complete example, in the form of a zip file or GitHub repo, that we might use to reproduce exactly what you're seeing?

[sean-mcmanus]

@Colengms clang++ gives an error, but g++ (and cl.exe) only gives a warning. IntelliSense is normally not supposed to give errors in warning cases.

But writing code that only compiles with g++ and not other compilers (or potential future g++ versions) isn't recommended.

[sean-mcmanus]

I've filed a bug on our shared VS parser at https://developercommunity.visualstudio.com/t/C-IntelliSense-gives-error-for-operato/10809064