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
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
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
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
