Once a name has a fixed meaning it cannot be changed. Using it at a point where the meaning is unambiguous resolves that meaning. This is inherently temporal. The recommended pattern in programs is to put the imports at the top all in one place. Then you’ll never encounter this issue except at the REPL.
StefanKarpinski
106
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Function name conflict: ADL / function merging? | 212 | 15333 | April 30, 2018 | |
| Possibility of `local import` statements in future? | 63 | 4135 | May 2, 2018 | |
| "Meaning", type-piracy, and method merging | 68 | 5561 | June 3, 2018 | |
| Proposal for SharedFunctions.jl package for optional dependency management | 74 | 6053 | May 7, 2019 | |
| Is Julia's way of OOP superior to C++/Python? Why Julia doesn't use class-based OOP? | 146 | 34211 | October 11, 2021 |