`<typeinfo>` unconditionally included on dinkumware
- Dominant language
- C++
- Stars
- 80
- Forks
- 184
- Avg merge
- 1h 16m
- Merged PRs (30d)
- 3
Description
It was added in 668b3fccaef7460036a1a83a9c90df8cbe76c4ab to fix lexical_cast (https://svn.boost.org/trac10/ticket/4115) problem, but that seems to be an overkill (and probably not needed since https://github.com/boostorg/lexical_cast/commit/3ce36a28484b76fab2dd96e8ee43f52ae87d1353?).
Also, it is a strange thing that with defined `BOOST_NO_STD_TYPEINFO` there is `std::typeinfo`. It completely undermines the purpose of the macro and of `boost/core/typeinfo.hpp`.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing commit 668b3fccaef7460036a1a83a9c90df8cbe76c4ab and the related lexical_cast commit 3ce36a28484b76fab2dd96e8ee43f52ae87d1353. Trace where is included for Dinkumware and how BOOST_NO_STD_TYPEINFO and boost/core/typeinfo.hpp are intended to interact; done means the compatibility fix remains valid without an unconditional inclusion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100