JakeHillion/object-introspection
1
0
Fork 0
mirror of https://github.com/JakeHillion/object-introspection.git synced 2024-09-19 19:19:05 +01:00
Code Issues Packages Projects Releases Wiki Activity
ed5fcfef9e
object-introspection/test/integration/folly_sorted_vector_map.toml

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

51 lines
2.7 KiB
TOML
Raw Normal View History

Types: Fix folly::small_vector and folly::sorted_vector_map folly::sorted_vector_map's results are not completely accurate, but at least CodeGen v2 matches CodeGen v1 for it now.
2023-07-25 17:14:59 +01:00
includes = ["folly/sorted_vector_types.h", "vector"]
[cases]
[cases.int_int_empty]
param_types = ["const folly::sorted_vector_map<int, int>&"]
setup = "return {};"
expect_json = '[{"staticSize":24, "dynamicSize":0, "exclusiveSize":24, "length":0, "capacity":0, "elementStaticSize":8}]'
tbv2: calculate total memory footprint Add the option to calculate total size (inclusive size) by wrapping the existing iterator. This change provides a new iterator, `SizedIterator`, which wraps an existing iterator and adds a new field `size` to the output element. This is achieved with a two pass algorithm on the existing iterator: 1. Gather metadata for each element. This includes the total size up until that element and the range of elements that should be included in the size. 2. Return the result from the underlying iterator with the additional field. This algorithm is `O(N)` time on the number of elements in the iterator and `O(N)` time, storing 16 bytes per element. This isn't super expensive but is a lot more than the current algorithm which requires close to constant space. Because of this I've implemented it as a wrapper on the iterator rather than on by default, though it is now on in every one of our integration test cases. Test plan: - Added to the integration tests for full coverage.
2024-01-03 17:30:31 +00:00
expect_json_v2 = '[{"staticSize":24, "exclusiveSize":24, "size":24, "length":0, "capacity":0, "members":[]}]'
Types: Fix folly::small_vector and folly::sorted_vector_map folly::sorted_vector_map's results are not completely accurate, but at least CodeGen v2 matches CodeGen v1 for it now.
2023-07-25 17:14:59 +01:00
[cases.int_int_some]
param_types = ["const folly::sorted_vector_map<int, int>&"]
setup = "return {{ {1,2}, {3,4} }};"
expect_json = '[{"staticSize":24, "dynamicSize":16, "exclusiveSize":40, "length":2, "capacity":2, "elementStaticSize":8}]'
tbv2: calculate total memory footprint Add the option to calculate total size (inclusive size) by wrapping the existing iterator. This change provides a new iterator, `SizedIterator`, which wraps an existing iterator and adds a new field `size` to the output element. This is achieved with a two pass algorithm on the existing iterator: 1. Gather metadata for each element. This includes the total size up until that element and the range of elements that should be included in the size. 2. Return the result from the underlying iterator with the additional field. This algorithm is `O(N)` time on the number of elements in the iterator and `O(N)` time, storing 16 bytes per element. This isn't super expensive but is a lot more than the current algorithm which requires close to constant space. Because of this I've implemented it as a wrapper on the iterator rather than on by default, though it is now on in every one of our integration test cases. Test plan: - Added to the integration tests for full coverage.
2024-01-03 17:30:31 +00:00
expect_json_v2 = '''[{"staticSize":24, "exclusiveSize":24, "size":40, "length":2, "capacity":2, "members":[
{"staticSize":8, "exclusiveSize":0, "size":8, "members": [
{"name":"key", "staticSize":4, "exclusiveSize":4, "size":4},
{"name":"value", "staticSize":4, "exclusiveSize":4, "size":4}
oil v2
2023-08-16 20:40:36 +01:00
]},
tbv2: calculate total memory footprint Add the option to calculate total size (inclusive size) by wrapping the existing iterator. This change provides a new iterator, `SizedIterator`, which wraps an existing iterator and adds a new field `size` to the output element. This is achieved with a two pass algorithm on the existing iterator: 1. Gather metadata for each element. This includes the total size up until that element and the range of elements that should be included in the size. 2. Return the result from the underlying iterator with the additional field. This algorithm is `O(N)` time on the number of elements in the iterator and `O(N)` time, storing 16 bytes per element. This isn't super expensive but is a lot more than the current algorithm which requires close to constant space. Because of this I've implemented it as a wrapper on the iterator rather than on by default, though it is now on in every one of our integration test cases. Test plan: - Added to the integration tests for full coverage.
2024-01-03 17:30:31 +00:00
{"staticSize":8, "exclusiveSize":0, "size":8, "members": [
{"name":"key", "staticSize":4, "exclusiveSize":4, "size":4},
{"name":"value", "staticSize":4, "exclusiveSize":4, "size":4}
oil v2
2023-08-16 20:40:36 +01:00
]}
]}]'''
[cases.int_int_reserve]
param_types = ["const folly::sorted_vector_map<int, int>&"]
setup = '''
folly::sorted_vector_map<int, int> m{{ {1,2}, {3,4} }};
m.reserve(10);
return m;
'''
expect_json = '[{"staticSize":24, "dynamicSize":80, "exclusiveSize":104, "length":2, "capacity":10, "elementStaticSize":8}]'
tbv2: calculate total memory footprint Add the option to calculate total size (inclusive size) by wrapping the existing iterator. This change provides a new iterator, `SizedIterator`, which wraps an existing iterator and adds a new field `size` to the output element. This is achieved with a two pass algorithm on the existing iterator: 1. Gather metadata for each element. This includes the total size up until that element and the range of elements that should be included in the size. 2. Return the result from the underlying iterator with the additional field. This algorithm is `O(N)` time on the number of elements in the iterator and `O(N)` time, storing 16 bytes per element. This isn't super expensive but is a lot more than the current algorithm which requires close to constant space. Because of this I've implemented it as a wrapper on the iterator rather than on by default, though it is now on in every one of our integration test cases. Test plan: - Added to the integration tests for full coverage.
2024-01-03 17:30:31 +00:00
expect_json_v2 = '''[{"staticSize":24, "exclusiveSize":88, "size":104, "length":2, "capacity":10, "members":[
{"staticSize":8, "exclusiveSize":0, "size":8, "members": [
{"name":"key", "staticSize":4, "exclusiveSize":4, "size":4},
{"name":"value", "staticSize":4, "exclusiveSize":4, "size":4}
oil v2
2023-08-16 20:40:36 +01:00
]},
tbv2: calculate total memory footprint Add the option to calculate total size (inclusive size) by wrapping the existing iterator. This change provides a new iterator, `SizedIterator`, which wraps an existing iterator and adds a new field `size` to the output element. This is achieved with a two pass algorithm on the existing iterator: 1. Gather metadata for each element. This includes the total size up until that element and the range of elements that should be included in the size. 2. Return the result from the underlying iterator with the additional field. This algorithm is `O(N)` time on the number of elements in the iterator and `O(N)` time, storing 16 bytes per element. This isn't super expensive but is a lot more than the current algorithm which requires close to constant space. Because of this I've implemented it as a wrapper on the iterator rather than on by default, though it is now on in every one of our integration test cases. Test plan: - Added to the integration tests for full coverage.
2024-01-03 17:30:31 +00:00
{"staticSize":8, "exclusiveSize":0, "size":8, "members": [
{"name":"key", "staticSize":4, "exclusiveSize":4, "size":4},
{"name":"value", "staticSize":4, "exclusiveSize":4, "size":4}
oil v2
2023-08-16 20:40:36 +01:00
]}
]}]'''
Types: Fix folly::small_vector and folly::sorted_vector_map folly::sorted_vector_map's results are not completely accurate, but at least CodeGen v2 matches CodeGen v1 for it now.
2023-07-25 17:14:59 +01:00
[cases.int_vector_empty]
skip = "Wrong results" # https://github.com/facebookexperimental/object-introspection/issues/258
param_types = ["const folly::sorted_vector_map<int, std::vector<int>>&"]
setup = "return {};"
expect_json = '[{"staticSize":24, "dynamicSize":0, "exclusiveSize":24, "length":0, "capacity":0, "elementStaticSize":32}]'
[cases.int_vector_some]
skip = "Wrong results" # https://github.com/facebookexperimental/object-introspection/issues/258
param_types = ["const folly::sorted_vector_map<int, std::vector<int>>&"]
setup = "return {{ {1,{2,3}}, {4,{5,6,7}} }};"
#expect_json = "TODO"
Reference in New Issue Copy Permalink