Compliance with style guide (partial) (2)

[ivanperez-keera]

Description

In our effort to move Copilot to Class D, we have to comply with a style guide. In order to progressively follow those rules, we split complying with the style guide into a number of smaller style-related issues.

This is the second issue pertaining to style changes for conformance with Class D.

Type

• Management: conformance with new requirement.

Additional context

• See #316 for other style changes addressed.

Requester

• Ivan Perez

Method to check presence of bug

Not applicable (not a bug).

Expected result

All Copilot code conforms to the following rules:

• All exports should be explicit.
• All imports should be explicit.
• Imports should be grouped, sorted, alphabetized, and aligned.
• The standard indendation is 2 spaces.
• Always leave a space after a comma.
• Do not require unnecessary pragmas.
• Do not add unnecessary imports.
• Do not include redundant brackets, except where the brackets are meant to communicate a conceptual unit.
• Do not include redundant $.
• Whenever possible, prefer simpler solutions and expressions.
• Use haddock formatting to capture copyright notices.
• Prefer guards to multiple nested if-then-else.

Desired result

All code complies with the rules above.

Proposed solution

Make all code comply with the rules above.

Further notes

None.