The name conflict part of the issue has been solved by #102062.

Now, there's still merit in discussing whether we want to make the macro PRINT_VERBOSE for consistency with usual macro naming style, or keep it lower case for consistency with print_line and print_error functions.

I'm personally more for the latter, but I wouldn't strongly oppose the former if there's consensus that it's the way to go.

The name conflict part of the issue has been solved by #102062.

It fixes it on the Godot side. We still kind of have it on the godot-cpp side, although, we're working around it by making it a function, and maybe have a couple other options to work around it if we want print_verbose() to be a macro there too.

Now, there's still merit in discussing whether we want to make the macro PRINT_VERBOSE for consistency with usual macro naming style, or keep it lower case for consistency with print_line and print_error functions.

There are semantic differences between functions and macros, so I'd personally be for PRINT_VERBOSE so it's clear that it's a macro, avoiding any confusion. That said, this isn't a very big problem :-)