Investigate improving (or removing) support for memoization
@kfirapps is already working on this.
Since Apr 15, 2019.
Assessment
This issue has not been assessed yet.
Description
Support for memoization is a bit dubious at the moment. If it is something that should continue to be supported documentation must be added. There may also be opportunities to simplify the API as well.
On the other hand, if memoization is not something that should be supported it should be removed.
- Dominant language
- Objective-C++
- Stars
- 5.7k
- Forks
- 574
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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 facebook/componentkit
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
facebook/componentkit#979 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
facebook/componentkit#977 · 1 comment ·
-
Abandoned? Open
Difficulty 5/5 Over a week Newbie friendliness 10/100
facebook/componentkit#976 · 2 reactions ·
-
Difficulty 1/5 Under an hour Newbie friendliness 45/100
facebook/componentkit#975 ·
-
Yoga-internal.h:135:11: error: definition of implicit copy constructor for 'Values<9>' is deprecated Open
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
facebook/componentkit#974 · 3 reactions ·