Import name shadows procedure with the same name

[obiwan87]

Description:
In shoco.odin, I found that the symbol compress is declared by both an import statement and a procedure.Instead of getting an error like "identifier compress already defined", the imported name silently takes precedence over the local one.

Example:

import "path/to/apackage"

// The imported `apackage` takes precedence over the local `apackage` procedure.
p :: proc() -> apackage.Some_Type {
}

apackage :: proc () {
}

What happens:

The imported name apackage is used, and the local procedure apackage is ignored. This compiles without errors.

What I expected:

An error about a name conflict, like:
identifier apackage already defined

How Go handles it:

In Go, if an imported package name conflicts with a local identifier, the compiler throws an error:

Question:

Is this behavior intentional? It feels a bit unintuitive. Should imports really take precedence over local definitions?