Is it bad form to put code in package.d other than imports?

Soulsbane paul at acheronsoft.com
Wed Jan 3 08:04:53 UTC 2018


On Wednesday, 3 January 2018 at 07:43:52 UTC, Jonathan M Davis 
wrote:
> On Wednesday, January 03, 2018 06:10:10 Soulsbane via 
> Digitalmars-d-learn wrote:
>> [...]
>
> The entire reason that the package.d feature was added was so 
> that it would be possible to split a module into a package 
> without breaking code. Anything beyond that was beyond the 
> scope of the purpose of the feature, albeit not necessarily in 
> conflict with its original purpose.
>
> [...]

Wow! Thanks Johnathan for the thorough explanation!


More information about the Digitalmars-d-learn mailing list