Subject: [boost] [multiprecision] Huge testcase datafile in commit r79802
From: Lars Viklund (zao_at_[hidden])
Date: 2012-07-30 14:59:02
My boost-commit@ mbox made my mail agent go into a nice crawl today when
displaying the commit details for r79802.
It turns out that it's about 6.3 MiB large, most of which is a massive
100k line test case in
Will this behemoth file end up in the real repository in case of library
acceptance, and even worse, will it end up in the deployed tarballs?
Are there any guidelines on keeping tests neat, or possibly generating
performance test data if it's excessively huge?
While in the discussion, has there been any thoughts of separating
documentation from the tree, and/or having codegen of the source files
that are clearly generated (vector200.hpp, etc.) in the build tree?
It's very straining on disk space to have multiple Boost trees lying
around, particularly if you're working in some kind of homedir
-- Lars Viklund | zao_at_[hidden]
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk