diff options
| author | Philip Withnall <philip.withnall@collabora.co.uk> | 2015-11-06 12:42:11 +0100 |
|---|---|---|
| committer | Philip Withnall <philip.withnall@collabora.co.uk> | 2015-11-06 12:45:04 +0100 |
| commit | d8e257464bd93ea502740169887297fa62925a16 (patch) | |
| tree | f43cd0266e2413ff5ea85dc1fb9ae523d27f7ab6 /giscanner/maintransformer.py | |
| parent | 54a5ed77c9c1296c7709c80428dc41d535999798 (diff) | |
| download | gobject-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 'giscanner/maintransformer.py')
| -rw-r--r-- | giscanner/maintransformer.py | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/giscanner/maintransformer.py b/giscanner/maintransformer.py index b4b39345..23ed4102 100644 --- a/giscanner/maintransformer.py +++ b/giscanner/maintransformer.py @@ -649,6 +649,7 @@ class MainTransformer(object): # gpointer parameters and return values are always nullable unless: # - annotated with (type) and not also with (nullable); or + # - annotated with (element-type) and not also with (nullable); or # - annotated (not nullable) # See: https://bugzilla.gnome.org/show_bug.cgi?id=719966#c22 if node.type.is_equiv(ast.TYPE_ANY): |