On 2014-01-10 00:34, H. S. Teoh wrote:

Yeah, any public imports should be mentioned somewhere in the docs,
otherwise it's just random invisible magic as far as the end-user is
concerned ("Hmm, I imported std.string in one module, and array.front
works, but in this other module, array.front doesn't work! Why? Who
knows.");

Please submit a pull request to add that to the docs.

I agree, and it should be automatic.

--
/Jacob Carlborg

Reply via email to