Dmitrii Kovanikov

These instances truncate characters. We already have an inspection for `ByteString.Char8.pack` and the relevant mechanism. So it should be pretty straightforward to implement this one as well.

If you define a typeclass like `MonadBlah`, it should have `Monad` in its context: ```haskell class Monad m => MonadBlah m where ```

Usages of these functions have the problems described in the following blog post: * https://www.snoyman.com/blog/2016/12/beware-of-readfile/ And suggest using `ByteString.readFile` + `decodeUtf8`

Proposed here: https://github.com/kowainik/stan/issues/44#issuecomment-640856753 We want to implement an ability to specify when Stan should exit with non-zero code. This is useful for running Stan on CI. But since different projects...

In the form: ``` path/to/file.hs:line:col-line2:col2 stuff ``` There are two questions: 1. What would the the CLI option name? 🤔 2. what to put into "stuff"?

Suggest `Text` and `ByteString` instead of `String`

2

We discussed this with @vrom911 and decided that it would be nice to suggest more efficient string types in the following places: 1. Data type fields. 2. Function return arguments.

Consider the following code: ```haskell data RowLen = RowLen { rowLenModule :: !Int , rowLenLine :: !Int , rowLenSev :: !Int , rowLenMax :: !Int , rowLenAvg :: !Int }...

For some inspections, it's possible to provide an unambiguous solution (e.g. STAN-0206), so we can refactor code automatically and fix some issues that will take a lot of time to...

Currently Stan panics when GHC versions are different. But it's possible to implement a check with a good error message. This check wouldn't be needed if the following GHC feature...

`fromIntegral` produces unexpected results for almost all types and is partial for `Natural`. We can recommend safer versions of this function. * `toIntegralSized` from `base` Additionally, we can add possible...