summaryrefslogtreecommitdiff
path: root/tests/scanner/Regress-1.0-sections-expected.txt
diff options
context:
space:
mode:
authorPhilip Withnall <philip.withnall@collabora.co.uk>2015-11-06 12:42:11 +0100
committerPhilip Withnall <philip.withnall@collabora.co.uk>2015-11-06 12:45:04 +0100
commitd8e257464bd93ea502740169887297fa62925a16 (patch)
treef43cd0266e2413ff5ea85dc1fb9ae523d27f7ab6 /tests/scanner/Regress-1.0-sections-expected.txt
parent54a5ed77c9c1296c7709c80428dc41d535999798 (diff)
downloadgobject-introspection-d8e257464bd93ea502740169887297fa62925a16.tar.gz
tests: Add more regression tests for (not nullable)
On bug #719966, the question arose of whether parameters annotated with (element-type) but not (not nullable) are regarded as nullable or non-nullable. Add some new unit tests to Regress-1.0.gir to check the behaviour is as expected: annotating a parameter with (element-type) implicitly makes it non-nullable (unless also annotated with (nullable)). https://bugzilla.gnome.org/show_bug.cgi?id=757678
Diffstat (limited to 'tests/scanner/Regress-1.0-sections-expected.txt')
-rw-r--r--tests/scanner/Regress-1.0-sections-expected.txt2
1 files changed, 2 insertions, 0 deletions
diff --git a/tests/scanner/Regress-1.0-sections-expected.txt b/tests/scanner/Regress-1.0-sections-expected.txt
index e0f9a1b7..c7ba75c6 100644
--- a/tests/scanner/Regress-1.0-sections-expected.txt
+++ b/tests/scanner/Regress-1.0-sections-expected.txt
@@ -343,6 +343,8 @@ regress_forced_method
regress_test_obj_instance_method
regress_test_obj_instance_method_callback
regress_test_obj_instance_method_full
+regress_test_obj_not_nullable_element_typed_gpointer_in
+regress_test_obj_not_nullable_typed_gpointer_in
regress_test_obj_set_bare
regress_test_obj_skip_inout_param
regress_test_obj_skip_out_param