Best practice: modules and scripts for publishing

I used to rely on Pkg.test(), which had the nice property of taking care of test-specific dependencies (or, in this case, use-case-specific dependencies, as opposed to dependencies required by the code under the src/ dir). However, I don’t think I would recommend (ab)using Pkg.test() any more for running plain use cases (as opposed to unit tests), especially since I recently realized that Pkg.test() did a lot more than what I initially thought. In particular, it sets --check-bounds=yes , which is a very sensible thing to do for tests, but impacts the performance for “regular” use cases.

1 Like