Absolute or relative imports?

[navidcy]

I'm wondering whether in submodules it's better to import via absolute, e.g., like

Oceananigans.jl/src/AbstractOperations/AbstractOperations.jl

Line 11 in b1b07fe

using Oceananigans.Fields: AbstractField, instantiated_location

or relative, e.g.,

 using ..Fields: AbstractField, instantiated_location 

?

Is there a reason for one vs the other?

cc @giordano

[giordano]

I don't think there's a technical benefit of one versus the other. The relative one is of course shorter, but besides that I don't think it has significant advantages.

[navidcy]

Thanks!

[glwagner]

I prefer absolute imports because they are more explicit. I also find them easier to read because names are references with absolute paths, ie

using Oceananigans.Fields: AbstractField

onlyu works if there is a name Oceananigans.Fields.AbstractField.

[giordano]

I prefer absolute imports

Oh, interesting, in Breeze relative imports seem to be somewhat popular 🙂

[glwagner]

damn the maps

[navidcy]

I like relative because it immediately tells me that this is an import from this package somewhere.
But I don't have strong preference!

[glwagner]

fair point. but what say you to the challenge of counting very.small..dots...