Sonja Heinze

Cool. > I guess for building documentation each package should be built separately as well. Oh, that's a very good point! So in the end it seems like that fixing...

Aah, I see. Thanks! (I'll be on new year's vacation from tomorrow on, but I can see if it's as simple as I think when I'm back)

Thanks @Leonidas-from-XIV, also for already giving quite some detail on this issue! I'm about to start working on this. I've just had a look and the current flow of `tag`...

About the idea of a matrix representation: I like the idea for the README, where we could associate one of the values `relevant` or `irrelevant` to a pair (lint check,...

Thanks @sim642 for opening and working on this! Are you also working or would like to work on the missing one, i.e. polymorphism handling? I was just ask by someone...

Thanks for reporting this! > Am I using the feature the way it was meant to be used? Perhaps linters produced by ppxlib are supposed to be used differently with...

We now have some more information about your question [here](https://github.com/ocaml/dune/issues/5238#issuecomment-985594308). So I think the `lint_impl` and `lint_intf` arguments of the ppxlib driver are unrelated to dune's `lint` stanza. My understanding...

> to use the `-null` argument for the `lint` task, which silences those warnings. In fact the `-null` argument silences everything, not just warnings. When passing in `-null`, the ppxlib...

Thanks for the context! It's very good to understand that the idea for the dune `(lint ...)` field is to avoid PPX as a hard dependency. By the way, how...

Hi @mbacarella, thanks for porting your ppx to `ppxlib`! When you use `ppxlib`, the migration is done by `ppxlib` itself, so you don't need to do anything in that regard....