-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dunai
: Consistency of Haskell code style (part 2)
#285
Labels
Milestone
Comments
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
We set the code limit for Haskell files at 80 characters. A "character" means any Unicode code point. Any line that would exceed this limit should be line-wrapped.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
We set the code limit for Haskell files at 80 characters. A "character" means any Unicode code point. Any line that would exceed this limit should be line-wrapped.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
We set the code limit for Haskell files at 80 characters. A "character" means any Unicode code point. Any line that would exceed this limit should be line-wrapped. We break move a definition in a where clause to a new line because it goees over 80 columns. Technically, those could be two different style rules being applied.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
We set the code limit for Haskell files at 80 characters. A "character" means any Unicode code point. Any line that would exceed this limit should be line-wrapped.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
We set the code limit for Haskell files at 80 characters. A "character" means any Unicode code point. Any line that would exceed this limit should be line-wrapped.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
We set the code limit for Haskell files at 80 characters. A "character" means any Unicode code point. Any line that would exceed this limit should be line-wrapped.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
We set the code limit for Haskell files at 80 characters. A "character" means any Unicode code point. Any line that would exceed this limit should be line-wrapped.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
A single space should also appear after the comma (,) in lists and tuples.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
A single space should also appear after the comma (,) in lists and tuples.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
A single space should also appear after the comma (,) in lists and tuples.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
A single space should also appear after the comma (,) in lists and tuples.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
A single space should also appear after the comma (,) in lists and tuples.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be grouped between external imports, external imports from the same project (but different libraries) and internal imports. When groups are used, comments must be used to indicate the nature of each group.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be grouped between external imports, external imports from the same project (but different libraries) and internal imports. When groups are used, comments must be used to indicate the nature of each group.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be grouped between external imports, external imports from the same project (but different libraries) and internal imports. When groups are used, comments must be used to indicate the nature of each group.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be grouped between external imports, external imports from the same project (but different libraries) and internal imports. When groups are used, comments must be used to indicate the nature of each group.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be grouped between external imports, external imports from the same project (but different libraries) and internal imports. When groups are used, comments must be used to indicate the nature of each group.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be grouped between external imports, external imports from the same project (but different libraries) and internal imports. When groups are used, comments must be used to indicate the nature of each group.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be grouped between external imports, external imports from the same project (but different libraries) and internal imports. When groups are used, comments must be used to indicate the nature of each group.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be grouped between external imports, external imports from the same project (but different libraries) and internal imports. When groups are used, comments must be used to indicate the nature of each group.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be grouped between external imports, external imports from the same project (but different libraries) and internal imports. When groups are used, comments must be used to indicate the nature of each group.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be grouped between external imports, external imports from the same project (but different libraries) and internal imports. When groups are used, comments must be used to indicate the nature of each group.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be grouped between external imports, external imports from the same project (but different libraries) and internal imports. When groups are used, comments must be used to indicate the nature of each group.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be grouped between external imports, external imports from the same project (but different libraries) and internal imports. When groups are used, comments must be used to indicate the nature of each group.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be grouped between external imports, external imports from the same project (but different libraries) and internal imports. When groups are used, comments must be used to indicate the nature of each group.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be grouped between external imports, external imports from the same project (but different libraries) and internal imports. When groups are used, comments must be used to indicate the nature of each group.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be grouped between external imports, external imports from the same project (but different libraries) and internal imports. When groups are used, comments must be used to indicate the nature of each group.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be grouped between external imports, external imports from the same project (but different libraries) and internal imports. When groups are used, comments must be used to indicate the nature of each group.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be explicit (aka. no wildcard imports).
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be explicit (aka. no wildcard imports). Remove import that is empty when made explicit.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be explicit (aka. no wildcard imports).
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be explicit (aka. no wildcard imports).
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be explicit (aka. no wildcard imports). Remove import that is empty when made explicit.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be explicit (aka. no wildcard imports). Remove import that is empty when made explicit.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be explicit (aka. no wildcard imports).
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be explicit (aka. no wildcard imports).
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be explicit (aka. no wildcard imports).
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be explicit (aka. no wildcard imports).
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be explicit (aka. no wildcard imports).
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be explicit (aka. no wildcard imports).
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be explicit (aka. no wildcard imports).
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be explicit (aka. no wildcard imports).
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be explicit (aka. no wildcard imports).
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be explicit (aka. no wildcard imports).
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be explicit (aka. no wildcard imports).
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be explicit (aka. no wildcard imports).
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be explicit (aka. no wildcard imports).
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be explicit (aka. no wildcard imports).
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be explicit (aka. no wildcard imports). Remove import that is empty when made explicit.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be explicit (aka. no wildcard imports).
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be explicit (aka. no wildcard imports).
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Imports should be explicit (aka. no wildcard imports). Remove import that is empty when made explicit.
ivanperez-keera
added a commit
that referenced
this issue
Jun 3, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Starting from this comment, I have looked at this Haskell style guide.
The text was updated successfully, but these errors were encountered: