Merge lp:~zorba-coders/zorba/fix-boost-typedef into lp:zorba
Proposed by
Federico Cavalieri
Status: | Merged |
---|---|
Approved by: | Paul J. Lucas |
Approved revision: | 11722 |
Merged at revision: | 11722 |
Proposed branch: | lp:~zorba-coders/zorba/fix-boost-typedef |
Merge into: | lp:zorba |
Diff against target: |
336 lines (+57/-65) 5 files modified
src/functions/cacheable_function.cpp (+15/-17) src/functions/cacheable_function.h (+10/-10) src/functions/external_function.cpp (+4/-6) src/functions/udf.cpp (+4/-4) src/zorbautils/hashmap_itemh_cache.h (+24/-28) |
To merge this branch: | bzr merge lp:~zorba-coders/zorba/fix-boost-typedef |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Paul J. Lucas | Approve | ||
Matthias Brantner | Approve | ||
Federico Cavalieri | Approve | ||
Review via email: mp+217976@code.launchpad.net |
Commit message
Removed boost dependency
Fixed typedef
Description of the change
Removed boost dependency
Fixed typedef
To post a comment you must log in.
The choice of the data structure to hold the flags is open to discussion.
I considered:
- std::bitset
- uint64
- vector<bool> (storage optimized specialization is mandated by the standard)
The size of std::bitset is determined at compile time, boost:dynamic_ bitset brings the boost dependency, so I went with vector<bool> because the structure will be non empty in exceptional cases. I preferred to not put a limit on function arity or deal with potential multiple bitfields.
No strong opinion though, comments are welcome.