Dmitrii Kovanikov

Something like this `length xs > 5` can be rewritten to handle infinite lists. This can be a separate inspection, or improved suggestion to the existing Infinite length inspection, if...

Suggest `0 < x && x < 10` instead of `x > 0 && x < 10`.

Tools like `weeder` can tell about unused top-level functions. But Stan can tell about unreachable code blocks. Something like this: ```haskell if True then ... else ```

It would be really nice if Stan can also include GHC warnings to its report. Having GHC proposals like [this one](https://github.com/ghc-proposals/ghc-proposals/pull/325) implemented will help a lot with implementing this feature.

Stan can output some false-positive results, when it sees the inspection, but it's not there: ```haskell foo = case xs of [] -> 0 _ -> head xs ``` We...

Sometimes, when the code is polymorphic, it's very easy to use the wrong order of fields: ```haskell data User = User { userName :: !Text , userAge :: !Int }...

[RFC] Inspection: function in `where` without type signature

2

Having functions in `where` blocks without type signatures makes code harder to understand and can lead to subtle compilation errors without a clear understanding of how to fix them. Should...

[RFC] Design API for specifying custom inspections

3

Users may want to introduce their own inspections (e.g. forbidding their partial functions). It would be nice to be able to support this API as well. My first thoughts (not...

Often it's required to compare different parts of AST on equality to provide various inspections. For this, we need to provide new constructors for `PatternAst` and be able to compare...

Improve STAN-0301 (missing infix) to handle more places where operator can be

1

Currently, operators which are defined inside typeclasses but missing fixity declaration, not reported. This can be fixed by matching operators as typeclass methods as well. The following AST pattern can...