namespace qualifiers::

[LukyGuyLucky]

Just to check whether my understanding is totally wrong--
So when a project contains several or dozens of modules,a lot of structs,constants,functions and methods inside these modules,now when making use of all these stuffs,we have to use namespace qualifiers on almost every of the aforementioned like below:

AAA::consts c;
BBB::enums e;
fn void CCC::functon(AAA:arg1,BBB::arg2,...){}
struct DDD
{
AAA::T t;
BBB::U u;
...
}
Is this mandatory or there is just option ways leave to user to just write like fn void function(arg1,arg2,...) ?

Thanks and best regards,
Peter

[lerno]

No that's not correct. You are required to use the shortened namespace on imported constants, globals, functions and macros. When I say "shortened namespace", I mean that if you have something like my_function in std::io::os, you only need to use os::my_function as long as that is unambiguous in the context. That is, you're not importing some other namespace like my::proj::os which has the exact same my_function.

For types (enums, struct, unions, distinct) the namespace is not required unless the name is ambiguous. Note also that the current module always take precedence. So if you have a Foo in your current module, and you import a module with Foo, you can use Foo without disambiguating it with a namespace, as the local Foo will always be assumed.

Even if you use a lot of modules, you should in general not need anything other than the required namespaces, that is the shortened namespace on constant/global/function/macro and no namespace on types.

Also, note that you never place the namespace on declarations.

[lerno]

The idea is that it's basically following C convention. So if there is a C function like this:

extern int raylib_do_something(int x);

With usage

int x = raylib_do_something(y);

Then the corresponding function / usage in C3 would be:

extern fn int do_something(int y);
...
int x = raylib::do_something(y);

[LukyGuyLucky]

Thanks.This seems good.

[LukyGuyLucky]

I am sorry but wait a moment please--

raylib_do_something(int y) vs
(raylib::)do_something(int y)
their signature are totally different.Would you please briefing what happened here?

[lerno]

If you would actually link against the C function called raylib_do_something you'd use @extern(...), like this:

extern fn int do_something(int y) @extern("raylib_do_something");

[LukyGuyLucky]

ah yes,I forgot we have @extern.

Appreicated.