Hubert Plociniczak 8c6fd60aaf Detect conflicts between exported types and FQNs (#5986) ... Exporting types named the same as the module where they are defined in `Main` modules of library components may lead to accidental name conflicts. This became apparent when trying to access `Problem_Behavior` module via a fully qualified name and the compiler rejected it. This is due to the fact that `Main` module exported `Error` type defined in `Standard.Base.Error` module, thus making it impossible to access any other submodules of `Standard.Base.Error` via a fully qualified name. This change adds a warning to FullyQualifiedNames pass that detects any such future problems. While only `Error` module was affected, it was widely used in the stdlib, hence the number of changes. Closes #5902. # Important Notes I left out the potential conflict in micro-distribution, thus ensuring we actually detect and report the warning.		2023-03-21 21:09:41 +00:00
..
data	Nightly proccess preparations: Setting Enso version through the environment (#3241)	2022-02-07 15:14:32 +01:00
src	Detect conflicts between exported types and FQNs (#5986)	2023-03-21 21:09:41 +00:00
package.yaml	Nightly proccess preparations: Setting Enso version through the environment (#3241)	2022-02-07 15:14:32 +01:00