Grzegorz Bielski

In addition, maybe we can re-export those data types from the main `index.ts`? Currently, you have to import them like this: ```typescript import { atRecord } from "monocle-ts/es6/At/Record"; ```

What about pointer events? MDN doc: https://developer.mozilla.org/en-US/docs/Web/API/Pointer_events This is a slightly newer API that covers more input methods and unifies mouse and touch events.

This error is very annoying. It basically prevents us from using given imports with `-Wunused:imports` so we have to rely on mixing in traits.

@som-snytt I didn't know about `-Wunused:strict-no-implicit-warn`. It helped, thx! > I don't think optional warnings (especially this one) are intended to invite architectural rewrites. My thoughts exactly! However, this was...

Hi @ruippeixotog, @jcazevedo, @leifwickland I know this is a bigger code piece, but please take a look if you have some time. 🙇 I think this will give us feature...

@Andrapyre This PR is focused mostly at improving derivation support in Scala 3. `pureconfig-yaml` is available for Scala 3 for 6 months now, and can be used as follows: (ported...

@ruippeixotog Thanks for taking a look! Please note that most of the changed lines in this PR come from tests copied almost verbatim from `pureconfig-generic`, and most of the changed...

@tjarvstrand I was able to get in touch with @ruippeixotog some time ago. He won't be available for the time being, but should return soon(ish) and hopefully some things will...

Thank you @ruippeixotog for providing this feedback, it's really invaluable! Having two derivation APIs - simple and more configurable one for advanced usage and cross-compilation sounds good to me. But...

> core shouldn't need to use any form of implicit-based hints That was the idea! I just think we need to keep the notion of hints in the `core`'s derivation...