Re: std.typecons.Flag -- public import for API users?

[rcorre via Digitalmars-d-learn]

On Tuesday, 24 March 2015 at 16:41:28 UTC, Rene Zwanenburg wrote:
Should not be necessary. privately import Flag and make a 
public alias:


module a;
import std.typecons : Flag;

alias SomeFlag = Flag!SomeFlag;

SomeFlag.Yes and SomeFlag.No should be usable in other modules 
without additional imports.


Nice idea Rene, thanks!

Re: std.typecons.Flag -- public import for API users?

[Rene Zwanenburg via Digitalmars-d-learn]

On Saturday, 21 March 2015 at 23:16:39 UTC, rcorre wrote:
If I am developing a library and some of my functinos take a 
std.typecons.Flag as an argument, should I 'public import 
std.typecons: Flag, Yes, No'?


It seems like it would be a pain for users of the library to 
have to import this separately whenever they use my library, 
but I'm not sure what the stance is on having your modules 
`public import` standard-library modules.


In general, is it considered bad form to 'public import' 
modules from phobos?


Should not be necessary. privately import Flag and make a public 
alias:


module a;
import std.typecons : Flag;

alias SomeFlag = Flag!SomeFlag;

SomeFlag.Yes and SomeFlag.No should be usable in other modules 
without additional imports.

std.typecons.Flag -- public import for API users?

[rcorre via Digitalmars-d-learn]

If I am developing a library and some of my functinos take a 
std.typecons.Flag as an argument, should I 'public import 
std.typecons: Flag, Yes, No'?


It seems like it would be a pain for users of the library to have 
to import this separately whenever they use my library, but I'm 
not sure what the stance is on having your modules `public 
import` standard-library modules.


In general, is it considered bad form to 'public import' modules 
from phobos?

Re: std.typecons.Flag -- public import for API users?

[ketmar via Digitalmars-d-learn]

On Sat, 21 Mar 2015 23:16:37 +, rcorre wrote:

 If I am developing a library and some of my functinos take a
 std.typecons.Flag as an argument, should I 'public import std.typecons:
 Flag, Yes, No'?
 
 It seems like it would be a pain for users of the library to have to
 import this separately whenever they use my library, but I'm not sure
 what the stance is on having your modules `public import`
 standard-library modules.
 
 In general, is it considered bad form to 'public import' modules from
 phobos?

i believe that there is nothing wrong in such public import in this 
particular case.

signature.asc
Description: PGP signature