RELOAD!

[Phrancis/AdventOfCode] 4 commits. 23 additions. 5 deletions.

[rubberduck-vba/Rubberduck] 7 commits. 2 issue comments. 323 additions. 374 deletions.

[SimonForsberg/minesweeper-server] 12 commits.

[Zomis/AdventOfCode2017] 7 commits. 211 additions. 132 deletions.

[rubberduck-vba/Rubberduck] bclothier synchronized pull request #3588: Feature extract method Update 2

[rubberduck-vba/Rubberduck] bclothier synchronized pull request #3588: Feature extract method Update 2

[rubberduck-vba/Rubberduck] bclothier synchronized pull request #3588: Feature extract method Update 2

[rubberduck-vba/Rubberduck] Vogel612 commented on Rubberduck.VBEEditor/Extensions/CodeModuleExtensions.cs of pull request #3588: Feature extract method Update 2

[rubberduck-vba/Rubberduck] rkapka assigned rkapka to issue #32: Handle runtime errors

[rubberduck-vba/Rubberduck] rkapka commented on issue #32: Handle runtime errors

> Is adding parse tree listeners still not advised? I can't see how it would be possible to implement this inspection without one.

[rubberduck-vba/Rubberduck] Vogel612 commented on issue #32: Handle runtime errors

> @rkapka that was back when each ParseTreeListener ran in a separate ParseTreeWalk. It's not remotely that problematic to register ParseTreeListeners now, since we can dispatch all walking events to a collection of listeners. As @retailcoder mentioned above: this inspection requires a simple parse-tree listener