Jay Kamat e27f725a85 Avoid following weak_ptrs ... Previously, we treated weak_ptrs as normal types and we recursed within them, following the internal data pointer and possibly causing crashes. We really shouldn't be following them, so I added a custom type to simply abort processing. If we want to handle them (ie: check if they are valid, and follow them if so), that should be fairly easy with the work there is here so far.		2023-03-28 14:10:27 -07:00
..
integration	Avoid following weak_ptrs	2023-03-28 14:10:27 -07:00
ci.oid.toml	Avoid following weak_ptrs	2023-03-28 14:10:27 -07:00
CMakeLists.txt	tests: build integration.py targets with cmake	2023-03-27 16:15:37 +01:00
integration_entry_doStuff_arg0.oid	Initial commit	2022-12-19 06:37:51 -08:00
integration_entry_doStuff_this.oid	Initial commit	2022-12-19 06:37:51 -08:00
integration_entry_inc_arg0.oid	Initial commit	2022-12-19 06:37:51 -08:00
integration_mttest.cpp	formatting: force pointers/references with the type	2023-03-24 20:18:18 +00:00
integration_return_incN_arg0.oid	Initial commit	2022-12-19 06:37:51 -08:00
integration_sleepy.cpp	formatting: force pointers/references with the type	2023-03-24 20:18:18 +00:00
integration.py	tests: build integration.py targets with cmake	2023-03-27 16:15:37 +01:00
mttest.h	formatting: force pointers/references with the type	2023-03-24 20:18:18 +00:00
test_compiler.cpp	formatting: force pointers/references with the type	2023-03-24 20:18:18 +00:00
test_parser.cpp	formatting: force pointers/references with the type	2023-03-24 20:18:18 +00:00