Clean up compat.

[reitermarkus]

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same change?
• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your changes? Here's an example.
• Have you successfully run brew style with your changes locally?
• Have you successfully run brew tests with your changes locally?

---

Always use this style:

module Compat
end

prepend Compat

[MikeMcQuaid]

There's still e.g. compat/formula.rb using the "open the existing class to overwrite the method" style; you might want to read through all the files in compat for comparison. This style is also taken by extend/os too if it made sense to clean that up in the same fashion.

[reitermarkus]

Well, prepend is only needed if the compatibility layer should be able to call the current implementation, i.e. super, but I guess we can use the same style anyways, just to be consistent.

[MikeMcQuaid]

Well, prepend is only needed if the compatibility layer should be able to call the current implementation, i.e. super, but I guess we can use the same style anyways, just to be consistent.

👍 Gotcha. I'm fine either way. For a future PR this does apply a bunch to the extend/os layer so doing it there too would be 🎉