3 ms·
But package.d could lead you to overdepend on too many modules too :) it's mostly great for end applications rather than internal to libraries.
by p0nce 8y ago
But package.d could lead you to overdepend on too many modules too :) it's mostly great for end applications rather than internal to libraries.
- ben-schaaf 8y agoSure, but that's not specific to package.d. See the earlier convention of all.d or d.d. That's the trade-off with having public imports. I don't see how this is related to my comment though?