Hi,
Just interesting does import order matter? it could be anything performance/override...
For example here this (I know some modules can be omitted).
In reality howeverâdue presumably to unresolved bugsâorder can end up mattering whenever some of the imports have modifiers. The compiler applies the first one it sees, and then when it comes to the next instance of a similarâlooking import, it may think it is already covered and not realize it needs to elevate the access. Modifiers that sometimes cause problems include @testable and @_exported. So if some imports appear to be malfunctioning, try putting the mostâelevated ones first. For example, if you make sure @testable imports are at the top, then even if something further down repeats the import in a narrower formâeven indirectlyâ, you will still have the testable access that was granted when the compiler first encountered it.
But donât bother worrying about this until you actually encounter a situation where the compiler gives you trouble. They are rare corner cases, and they arenât supposed to happen anyway. Odds are they get fixed before you ever encounter one.