Dmitrii Kovanikov

This commit doesn't use cpp-options but it catches errors in cpphs like those from issue description: https://github.com/serokell/importify/commit/27cc482278415af0914256152e58d988a2c993af

I wrote this in the comment section to other issue but this issue description looks better so I close previous issue as _duplicate_. > Thanks for creating issue! But first...

@jiegillet This is indeed an issue. I guess what we can do is to have two combinators: ``` lexeme lexemeNoLn ``` And use `lexemeNoLn` explicitly in places with `eol` combinator...

@jiegillet In order to implement this test, we need to do a lot of stuff... As I understand, `BurntSushi` test uses encoding via JSON. But in some specific format to...

@vrom911 Excellent idea 👌 It's totally possible because we already know this information during parsing. I think, the solution to this problem will be to implement a type like: ```haskell...

@vrom911 That's a nice idea :+1: I'm only thinking about possible UI. What if we don't want all tables to be printed as inline tables? In that case, maybe the...

`generic-match` looks promising for this! * https://github.com/SamuelSchlesinger/generic-match

@MitchStevens Maybe we also need to validate something else. It would really a great idea to walk through the whole TOML specification and find all places to analyse (researching existing...

@MitchStevens This is tricky question, actually. I need to think more about the possible design. For now, it's not obvious, how to implement this logic properly with existing code.

Currently `TOML` object is created using `fromList` function. I guess refactoring this in order to add validation will change code significantly. * https://github.com/kowainik/tomland/blob/6fe11cc2f79d742f0b7c9089bdfe70bf1b6aa776/src/Toml/Parser/TOML.hs#L45-L48