The nuke-boost TODO list

[sherm1]

Thanks to @scpeters in #100 for this list and idea. Please submit PRs that get rid of one or more of these and then check off the ones that are done until they are all gone. This issue is also a good place to discuss problems that arise.

• boost/test/unit_test.hpp
• boost/filesystem.hpp
• boost/timer.hpp
• boost/array.hpp
• boost/assert.hpp
• boost/assign/list_of.hpp
• boost/bind.hpp
• boost/cstdint.hpp
• boost/date_time/posix_time/posix_time.hpp
• boost/dynamic_bitset.hpp
• boost/foreach.hpp
• boost/function.hpp
• boost/iterator/zip_iterator.hpp
• boost/math/constants/constants.hpp
• boost/math/special_functions/erf.hpp
• boost/math/special_functions/fpclassify.hpp
• boost/noncopyable.hpp
• boost/random/lagged_fibonacci.hpp
• boost/random/mersenne_twister.hpp
• boost/random/normal_distribution.hpp
• boost/random/uniform_int.hpp
• boost/random/uniform_real.hpp
• boost/random/variate_generator.hpp
• boost/shared_array.hpp
• boost/shared_ptr.hpp
• boost/thread.hpp
• boost/thread/mutex.hpp
• boost/unordered_map.hpp
• boost/unordered_set.hpp
• boost/weak_ptr.hpp

[sherm1]

I got a response from Jia @panjia1983 regarding dynamics_bitset:

From: Jia Pan [mailto:panjia1983@gmail.com]
Sent: Friday, March 25, 2016 10:36 AM
To: Michael Sherman sherm@tri.global
Subject: Re: FCL notifications?

The morton code is used for some acceleration of multi-object collisions (Figure 2 in this paper: http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=6631081). It is just one acceleration choice, and it does not hurt much if being remove -- the user can always choose other ways for acceleration.

Not sure how to interpret that -- Jia, are you saying that if it is restricted to compile-time size then it won't be useful at all?

[jslee02]

All the boost dependencies are removed by #103, #104, #105, #108, #140, #146, #147, and #148!

Closing this issue.

[sherm1]

Yay -- look at that beautiful list of check marks! Thanks, JS and the rest of the boost-bashing team. 👍