boostorg / boostorg/multiprecision
Should expression templates be enabled by default as of 2024?
- Dominant language
- C++
- Stars
- 265
- Forks
- 128
- Avg merge
- 4h 48m
- Merged PRs (30d)
- 2
Description
Hi,
I just spent a couple of days hunting a bug that was caused by using "auto" with this library. I then found out that this is expected:
I wonder if it is a correct decision today, where "auto" is now very well established into the language, to ship a library that by default computes complete wrong results when using it with "auto".
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points and asks whether expression templates should be enabled by default. Start by locating the current expression-template default and the behavior demonstrated in the report. A decision on the default and corresponding documented or tested behavior would define what is done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100