Page MenuHomePhabricator

eolian: refactor inlist<> usage
Closed, InvalidPublic


The inlist should *only* accept values, no pointers, no classes.

Further more:

foo : inlist<char>

Should result in a struct definition, that contains the EINA_INLIST; header in FIRST place, and after that the type (by value!).

A owned inlist also passes owned content.

bu5hm4n created this task.Jan 21 2019, 5:05 AM
bu5hm4n triaged this task as High priority.
bu5hm4n renamed this task from eolian: refactor the inlist usage to eolian: refactor inlist<> usage.Jan 21 2019, 5:10 AM
bu5hm4n updated the task description. (Show Details)
q66 closed this task as Invalid.Feb 28 2019, 5:32 PM


will be re-implemented correctly from scratch next release