Construction and destruction?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
The issue proposes construction, destruction, allocation, and deletion operations but names no source files or tests. Start by reading the linked Boost Lambda construction and destruction documentation, then inspect lambda2's existing operation patterns. Done means the proposed operations and their aggregate forms have an agreed design and corresponding coverage.
Written by the indexing model from the issue text.
Description
I propose to do it like in a boost.lambda. Additionally adding aggregate and new_aggregated_ptr:
constructor<T>()(arg_list) T(arg_list)
aggregate<T>()(arg_list) T{arg_list}
destructor()(a) a.~A(), where a is of type A
destructor()(pa) pa->~A(), where pa is of type A*
new_ptr<T>()(arg_list) new T(arg_list)
new_aggregated_ptr<T>()(arg_list) new T{arg_list}
new_array<T>()(sz, val_list) new T[sz]{val_list}
delete_ptr()(p) delete p
delete_array()(p) delete[] p
- Dominant language
- C++
- Stars
- 25
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from boostorg/lambda2
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in boostorg/lambda2
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
objectionary/eo-graphs#74 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 88/100
QuantStack/git2cpp#187 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100