Thank you for your reply again. It's exactly what you said. The meaning of the namespace may be to emphasize the logical structure of files, making it easier to distinguish and better manage files. Just like the head office database can better manage the data of multiple branches, but if branch 1 wants to know the data information of branch 2, it still has to go to the head office to call it. This is like importing different files in the same namespace when they are used with each other. But at this time you can clearly know where to go to find the files you need in the potentially huge file system, just like you clearly know where to go to the database of your head office to find the data of the branch you need. The information is the same, because the file you need is in your namespace, and you can clearly locate the target file location. Therefore, the meaning of a namespace does not necessarily mean that files in the same space can be directly shared and visible. After thinking about it, you will find that if files in the same namespace are directly visible, it means that when running a file, you may have to Automatically load all files in this space, which consumes resources and most of the loaded files are not used. The significance of the namespace is that when you need a file, thanks to this file structure, it can help you quickly import the file you want, and then you can import individual files according to your own needs.