Skip to content

Compliance with style guide (partial) #316

@ivanperez-keera

Description

@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.

Type

  • Management: conformance with new requirement.

Additional context

None.

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 comments are line comments except for compiler options, language pragmas, and annotations/warnings/deprecations.
  • Contiguous block comments are alphabetized, given one per line, and horizontally aligned.
  • Never leave a white spaces between a value and a comma.
  • Do not include TODOs or FIXMES.
  • A where keyword always stands alone on a line (except for class/instance/data/module declarations).
  • No more than one empty line between definitions.
  • No horizontal lines to separate sections in code.
  • No trailing spaces.

Desired result

All code complies with the rules above.

Proposed solution

Make all code comply with the rules above.

Further notes

None.

Metadata

Metadata

Labels

CR:Status:ClosedAdmin only: Change request that has been completedCR:Type:ManagementAdmin only: Change request for conformance with policies or procedures

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions