>>105697569
Because there aren't better alternatives
> module.func
you end up with too many dots in your code: decimal point, records access, ranges
You should have clear syntax to differentiate between namespaces and data records
eg: nontrivial zig code snippets tend to look like a dot soup especially when dealing with a lot of data structure in modules that force you to have 3 level of indirection

module.data.func()

instead of a more clear

module::data.func()

which highlights what's the namespace and what's the data structure
>

 module$func()

just horrible
>

 module/func()

unreadable
>

 module:func()

okay-sh but already used for type variables declarations and also it's harder to read respect to other options
>

 module-func()

kebab case it's good for functional programming, it doesn't look so good in other paradigms

Unless you have a better proposal

module::func()

it's the least shitty option

Back | Go to board

Board:

/g/

Thread:

/chug/ - comfy hare users general