On 6/7/13, nazriel <[email protected]> wrote: > But still it looks weird to me that allowing access to > std.datetime.time.Clock via std.datetime.Clock, even though Clock > is defined in std.datetime.time and std.datetime.package is only > publicly importing it, is ok.
This could come as a benefit. For example, a user might not know exactly which modules a package module is composed of, so he'll instinctively try to type "std.datetime.time" and it will work.
