Lloyd

That looks reasonable to me. However, I just realised that we're talking about *Postgres* enums, and the Doobie integration we have so far, `enumeratum-doobie`, is **not** Postgres-specific, and I don't...

> Hi guys. Just curious – any progress on this issue? I also faced this issue in my project some time ago and came up with a similar solution eventually....

Pretty much straight port of Kaminari's method in my pull request https://github.com/mislav/will_paginate/pull/324

I've been exploring `bloop` for a large-ish Gradle work project recently (hence all the noise), and this is one of those features that I miss from SBT.

Interesting; I guess the empty enum trick has fallen out of fashion :) `Here` aside, should we wait until `!` as a type is stabilised before going ahead with getting...

That looks awesome !

I agree with @ExpHP 's assessment; this will be pretty difficult to implement with `HList`. I do wonder though : what is the use case for such a method, when...

I haven’t taken a thorough look (currently on vacation with spotty internet) but the proposed changes and feedback look reasonable to me :) Also :+1: for `poly_fn_mut!` perhaps being too...

Indeed, this was known and is noted in the [Transmogrification section](https://github.com/lloydmeta/frunk#transmogrifying) as well. It's a fairly annoying limitation, true, but I decided to add it because (1) it's still got...

> Ah, yes, I missed that warning text. Two follow on questions: > > 1. Do you need more than specialisation? I think you need the "lattice impl" extension (maybe...