List initialization problem
- Dominant language
- C++
- Stars
- 50
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Description
```cpp
boost::fusion::vector{ 123 }; // ok
boost::fusion::vector{ { 123 } }; // fail
boost::optional{ 123 }; // ok
boost::optional{ { 123 } }; // ok
boost::fusion::vector>{ 123 }; // ok
boost::fusion::vector>{ { 123 } }; // fail
boost::fusion::vector>{ { { 123 } } }; // fail
boost::fusion::vector{ "hello" }; // ok
boost::fusion::vector{ { "hello" } }; // fail
boost::optional{ "hello" }; // ok
boost::optional{ { "hello" } }; // ok
boost::fusion::vector>{ "hello" }; // fail
boost::fusion::vector>{ { "hello" } }; // fail
boost::fusion::vector>{ { { "hello" } } }; // fail
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the listed C++ initialization examples and comparing the failing nested-brace cases with the successful ones. The issue names no source files or tests, so completion would require identifying the relevant Boost.Fusion vector initialization entry point and confirming that the failing forms behave consistently with the intended forms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100