Sergey Torgashov

> Perhaps something like import org.typelevel.scalacoptions.warnings.dsl._ would be good? > Alternatively, we could nest all of the DSL classes inside an object `WarningConfig`. Then users could import org.typelevel.scalacoptions.WarningConfig._ or use...

I would say initially I was considering a package-like import paths everywhere. But I've kinda reconsidered that and now leaning towards just putting it into the `WarningConfig` object. Why? Just...

I feel that the canonical way of dealing with logger names would be passing a `LoggerFactory` instance to class constructors instead of the `Logger` itself. Then, a new class-related instance...

Would we consider bringing something like `Diet` from cats-collection into `scalac-option`, btw? Since it encodes sets of ranges of any type and allows their composition, it could be pretty helpful...

Ok.. But it won't work for options like `-encoding utf-8` because of a parameter passed separately 😊 I need to think harder :)

Yeah, personally I would really love to continue on this... Just got distracted a little bit with some other less pleasant but more urgent stuff, unfortunately. Hopefully, I will sort...

Should we close it or merge it?

One of the ways this could be alleviated is to create explicitly named `as*` methods which would be free of the `Encoder` requirements. For example, `JsonTraversalPath` and `JsonFoldPath` could get:...

Perhaps, we could consider consolidating some syntax like `OptionOps` and `TryOps` in one place – either "cats" or "mouse". Personally, I often feel a bit annoyed when I need import...

Hello @tomohavvk, thank you for your thorough work! I believe the support for range types will be a fantastic addition to Doobie! However, I would like to discuss some potential...