I've noticed the error disappears if this `valac` option is removed:
--enable-experimental-non-null
(I'm unlucky, as I love the idea of this kind of check).
As a workaround for now, running `valadoc` with the same option, does
not make it fails, checks the source and points any error about
conversion attempt like from `string?` to `string`. Finally I can
disable the option for compiling and keep it for document generation,
which becomes a kind of added check.
Would still be better if using this option would not result in invalid C
source generation.
How is it supposed to impact C source generation? Though it was only
about static checking...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1129863
Title:
Valac generates invalid C source (const gchar * + const char *)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vala-0.14/+bug/1129863/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
