- Feb 14, 2019
-
-
Szymon Romik authored
aggregate initialization is allowed for structs with no user-declared (explicitly defaulted or deleted constructors are allowed) constructors since C++11, but gcc 4.8.5 doesn't support it
-
- Feb 13, 2019
-
-
Szymon Romik authored
vector: non-member swap
-
Szymon Romik authored
test: fix pool's layout name
-
- Feb 12, 2019
-
-
Krzysztof Kajrewicz authored
-
Krzysztof Kajrewicz authored
Our swap() implementation is throwing.
-
Krzysztof Kajrewicz authored
-
Krzysztof Kajrewicz authored
-
Marcin Ślusarz authored
vector: add assign methods and operators
-
Krzysztof Kajrewicz authored
-
Krzysztof Kajrewicz authored
-
Krzysztof Kajrewicz authored
-
Szymon Romik authored
-
- Feb 08, 2019
-
-
kkajrewicz authored
vector: rm active tx assert in vector API
-
- Feb 07, 2019
-
-
Szymon Romik authored
verify if non-const access methods/iterators works out of tx scope
-
Szymon Romik authored
it is unsafe to use some access methods/operators (e.g. at(), begin()) out of transaction scope, however we can't forbid users to use them, because there is no other way to modify elements without transaction
-
Igor Chorążewicz authored
test: cover missing vector cases based on codecov analysis
-
Szymon Romik authored
Add overload for array.range() method.
-
Krzysztof Kajrewicz authored
-
Krzysztof Kajrewicz authored
-
- Feb 06, 2019
-
-
Igor Chorążewicz authored
minor fixes to helper classes
-
Igor Chorazewicz authored
This oveload takes only 2 parameters and snapshots the entire range immediately. Return value is slice<pointer> instead of slice<range_snapshotting_iterator<T>>. This change reduces overhead of moving iterators in case where entire range is snapshotted.
-
Szymon Romik authored
Change array modifiers (assignment operators, swap and fill) behaviour.
-
Krzysztof Kajrewicz authored
-
Igor Chorazewicz authored
-
Igor Chorazewicz authored
Those methods now start internal transaction so that they are seen as atomic from user's perspective. This behaviour is consistent with pmem::vector. Moreover those methods can be called only on pmem-resident objects. Unlike in pmem::vector we cannot check if object is on pmem in a constructor (because array is aggregate) so we postpone this to a swap/fill/operator= function call. This check is performed only in those functions bacause of performance overhead.
-
Szymon Romik authored
Remove string libcxx tests which won't be ported
-
kkajrewicz authored
refactor vector private methods
-
- Feb 05, 2019
-
-
Szymon Romik authored
Add get(args) method overload for v.
-
Igor Chorazewicz authored
These tests are either testing deduction guides (which won't be implemented) or using custom allocator, which cannot be used with pmem::obj::experimental::string.
-
Szymon Romik authored
-
Szymon Romik authored
Make vector's private methods more generic. It will be beneficial for implementing vector's modifiers methods.
-
Igor Chorążewicz authored
cmake: refactor the way we add tests to the project
-
Igor Chorazewicz authored
get(args) method forwards args to the objects constructor. operator= was only assuring that 'this' object was initialized by calling get. This patch also assures that object from which we assign is also initialized.
-
Krzysztof Kajrewicz authored
-
Krzysztof Kajrewicz authored
-
Marcin Ślusarz authored
Run tests with PMEM_IS_PMEM_FORCE=1
-
Marcin Ślusarz authored
Merge back changes from stable-1.5
-
Szymon Romik authored
Fix range_snapshotting iterator when snapshot_size == 0
-
Igor Chorazewicz authored
-
Igor Chorazewicz authored
-