GNOME Bugzilla – Bug 756088
giscanner.message: Don't print node as the default context
Last modified: 2015-10-06 06:40:36 UTC
Node is always present in the output of .log_node(), so printing it another time as context just adds noise.
Created attachment 312688 [details] [review] giscanner.message: Don't print node as the default context Node is always present in the output of .log_node(), so printing it another time as context just adds noise.
Review of attachment 312688 [details] [review]: OK, I think I see an example where this is better. Hope we're not losing context from somewhere though.
https://git.gnome.org/browse/gobject-introspection/commit/?id=e8a7fbee3bb652159b81771ec16eab938ff84793
(In reply to Colin Walters from comment #2) > Review of attachment 312688 [details] [review] [review]: > > OK, I think I see an example where this is better. Hope we're not losing > context from somewhere though. The way I understand it works is, there's either positions= and then the context is expected to be passed as well, or then the positions and context are taken from the AST node. If there were no positions set on the node, the default context repeated the node printout, but this time in repr.