The offset computation logic has been moved to
ide_word_completion_results_compare

Compute relative offsets during the sort as relative
offsets are tend to change according to sort_direction
requested by the user.

We do not want to risk having this fire while we have been unloaded but
before we've been disposed.

In case the extensions want to poke at the editor-view actions for some
reason, wait to clean those up until plugins have unloaded.

We were leaking extensions when we were disposed without first NULL'ing
out the matching extensions. This ensures that we cleanup any future
extensions in the dispose phase.

To avoid breaking expectations about having a valid self->extensions
hashtable, we replace a dummy hashtable in case the object tries to
outlive the GObjectClass.dispose call.

This helps us to ensure our pointer is always cleared when the widget is
destroyed.

We want to ensure our editor_view isn't in the destruction path when our
callback is executed. So just try to be a bit extra defensive here.

Lucie Dvorakova authored Aug 15, 2017 and Christian Hergert committed Aug 19, 2017

https://bugzilla.gnome.org/show_bug.cgi?id=785854

Anoop Chandu authored Aug 18, 2017 and Christian Hergert committed Aug 17, 2017

Using get_build_flags_for_files in IdeBuildSystem, build flags for multiple
files can be retrieved at a time.

Build systems can implement this optimize their parsing and lookup of flags
which can have a performance impact on features such as the code indexing
engine.

If a build system does not implement this feature, a fallback is provided to
lookup flags individually using get_build_flags_async().

We have lost this (<ctrl>i in Builder default keyboard mode)
in the UI revamp.

We lost this in the UI revamp

https://bugzilla.gnome.org/show_bug.cgi?id=786393

For shortcuts visible in the shortcuts window,
we need to set the "shortcut window" translation context

https://bugzilla.gnome.org/show_bug.cgi?id=786334