Profpatsch
Profpatsch
the `-v` flag does not work in release builds, because the `slog::debug!` macros are removed. We still want to keep them, since they enable better debugging.
When thinking about the problem, the one tool that immediately comes to mind is [hlint](https://hackage.haskell.org/package/hlint). In what way does your approach differ from e.g. auto-applying hlint suggestions? I would have...
Thus, it crashes. https://github.com/NixOS/npm2nix/blob/master/src/npm2nix.coffee#L201 https://github.com/NixOS/npm2nix/blob/master/src/npm2nix.coffee#L238 Yay for dynamically typed languages
At the moment the information extraction only uses one core max; a `-j` option would be nice since it could speed the whole thing up by orders of magnitude. See...
It’s hard to use a tool where you can’t check on the command line how it works.
When multiple columns are missing, `sv` will create an `UnexpectedEndOfRow` error for each row that is missing, example: ```haskell > decode ((,) int int) (Identity mempty) Failure (DecodeErrors (UnexpectedEndOfRow :|...
I’m trying to write a decoder which parses the whole remaining columns with the same decoder. Something like `remaining :: Decode e s a -> Decode e s [a]`. and...
I have a row that requires two fields to be set. Something akin to ``` foo Decode e s a) -> Decode e s a ` but similar to the...
I noticed that the parse errors contain neither line numbers nor column numbers (assigning a decoding error to a column). The first can be easily circumvented by parsing the file...
I have a datatype with a list of translations, like so: ``` type Lang = Text data Trans = Trans { key :: Text, translations :: [(Lang, Text)] } ```...