• Alexandr Druzhinin (25/25) Dec 05 2013 Hi all.
• Dicebot (6/8) Dec 05 2013 It depends on how bar uses foo. You should do public import of
• Alexandr Druzhinin (4/11) Dec 05 2013 Third module uses both Bar and Foo. So I should either import every
• Dicebot (6/23) Dec 05 2013 It does not matter what third module uses, it is purely about
• Alexandr Druzhinin (2/6) Dec 05 2013 I realized.

Alexandr Druzhinin <drug2004 bk.ru> writes:

Hi all.
How to use use selective imports more effectively? I have two modules 
foo and bar:

module foo;

class Foo {}

module bar;

import foo: Foo;

class Bar
{
	private Foo foo_;
	this(Foo foo)
	{
		foo_ = foo;
	}
}

Now I add module baz that use both modules above. How to import foo and 
bar - everything or only 'the topmost' one, bar?

module baz;

import bar: Bar;
import foo: Foo;

or

import bar: Bar, Foo; // also in bar import of foo.Foo should be public 
of course

I don't see difference, but it doesn't mean it doesn't exist. What do 
you think about it?

"Dicebot" <public dicebot.lv> writes:

On Thursday, 5 December 2013 at 11:17:18 UTC, Alexandr Druzhinin 
wrote:
 I don't see difference, but it doesn't mean it doesn't exist. 
 What do you think about it?

It depends on how bar uses foo. You should do public import of 
symbols from foo if they are required to interact with bar public 
API. If foo is only used as part of internal implementation, it 
should be kept private and both modules imported explicitly.

Alexandr Druzhinin <drug2004 bk.ru> writes:

05.12.2013 20:34, Dicebot пишет:
 On Thursday, 5 December 2013 at 11:17:18 UTC, Alexandr Druzhinin wrote:
 I don't see difference, but it doesn't mean it doesn't exist. What do
 you think about it?

 It depends on how bar uses foo. You should do public import of symbols
 from foo if they are required to interact with bar public API. If foo is
 only used as part of internal implementation, it should be kept private
 and both modules imported explicitly.

Third module uses both Bar and Foo. So I should either import every 
module individually, or import Bar only but Bar should publicly import 
Foo - that's the question.

"Dicebot" <public dicebot.lv> writes:

On Thursday, 5 December 2013 at 13:39:09 UTC, Alexandr Druzhinin 
wrote:
 05.12.2013 20:34, Dicebot пишет:
 On Thursday, 5 December 2013 at 11:17:18 UTC, Alexandr 
 Druzhinin wrote:
 I don't see difference, but it doesn't mean it doesn't exist. 
 What do
 you think about it?

 It depends on how bar uses foo. You should do public import of 
 symbols
 from foo if they are required to interact with bar public API. 
 If foo is
 only used as part of internal implementation, it should be 
 kept private
 and both modules imported explicitly.

 Third module uses both Bar and Foo. So I should either import 
 every module individually, or import Bar only but Bar should 
 publicly import Foo - that's the question.

It does not matter what third module uses, it is purely about 
relation between foo and bar. If foo symbols are not necessary 
part of public bar API, third module will import both. If they 
are, bar will import foo publicly. Pretty simple.

Alexandr Druzhinin <drug2004 bk.ru> writes:

05.12.2013 20:43, Dicebot пишет:
 It does not matter what third module uses, it is purely about relation
 between foo and bar. If foo symbols are not necessary part of public bar
 API, third module will import both. If they are, bar will import foo
 publicly. Pretty simple.

I realized.