АХ
Кулешевич отбивался от него руками и ногами. Можешь почитать PR 62 для истории
Size: a a a
2020 June 23
MK
Спасибо
AV
А для PatternSynonyms имена "полей" случайно нельзя писать?
AV
Ваще классно бы было (наверное)
AK
Почему если у меня есть instance Field "foo" Foo Foo Bar Bar, то
foo ^. #info . to(zzz) может не работать и говорить, что нет поля info?Во-первых, Field лучше не трогать и делать через HasField
AK
Во-вторых, скинь полную ошибку
AV
Уже разобрался
AV
Там дальше не то делал
AV
Во-первых, Field лучше не трогать и делать через HasField
но тогда у меня нет
#x синтаксиса?AV
Я могу писать только
^.field @x ?AV
хм, сделал HasField и всё сломалось
AV
• The type SmtTask does not contain a field named 'task'.
• In the second argument of ‘(^.)’, namely ‘#task’
In the first argument of ‘Generic.extractGroups’, namely
‘(t ^. #task)’AV
При том, что с Fields именно это работало
AV
и как у PatternSynonyms доказать exhaustiveness?
AV
О {-# COMPLETE #-}
🍔-
#haskell STatic ANalyser
Stan is a command-line tool for analysing Haskell projects and outputting discovered vulnerabilities in a helpful way with possible solutions for detected problems. Stan is searching for not only performance or error-prone code pieces, but it also can help with establishing and applying best-practices from the whole Haskell ecosystem.
Although Haskell is a statically typed language, not all properties can be encoded in types. Even though GHC is quite a powerful compiler, it tries to be library-agnostic and provide only language-specific suggestions, while Stan uses the knowledge about the current state of the ecosystem and commonly used libraries.
You will find Stan helpful if you enjoy writing in Haskell, but want more guarantees from your code, not provided by the Haskell type system or GHC.
Stan is a configurable CLI tool. Besides the main feature of analysing Haskell projects statically, Stan has a list of features that make it unique, easy to use and flexible to configure:
- Pretty analysis results, including both HTML and terminal reports
- Suggestions and possible solutions for fixing the existing problems
- Analysing not only Haskell source code, but also information from the .cabal files
- Flexible runtime configuration via TOML and CLI
https://github.com/kowainik/stan
Stan is a command-line tool for analysing Haskell projects and outputting discovered vulnerabilities in a helpful way with possible solutions for detected problems. Stan is searching for not only performance or error-prone code pieces, but it also can help with establishing and applying best-practices from the whole Haskell ecosystem.
Although Haskell is a statically typed language, not all properties can be encoded in types. Even though GHC is quite a powerful compiler, it tries to be library-agnostic and provide only language-specific suggestions, while Stan uses the knowledge about the current state of the ecosystem and commonly used libraries.
You will find Stan helpful if you enjoy writing in Haskell, but want more guarantees from your code, not provided by the Haskell type system or GHC.
Stan is a configurable CLI tool. Besides the main feature of analysing Haskell projects statically, Stan has a list of features that make it unique, easy to use and flexible to configure:
- Pretty analysis results, including both HTML and terminal reports
- Suggestions and possible solutions for fixing the existing problems
- Analysing not only Haskell source code, but also information from the .cabal files
- Flexible runtime configuration via TOML and CLI
https://github.com/kowainik/stan
AA
А для PatternSynonyms имена "полей" случайно нельзя писать?
можно, но вайлдкады с синонимами-рекордами вроде не работали
MK
Реклама ковайника...
AV
Я вот чуть не удалил
MK
Ага