pg_partman 3.0.0 - real-world usage of native partitioning and a casefor native default

Thankfully since native partitioning still uses inheritance internally for the most part, pg_partman works pretty well without nearly as much change as I thought I would need. The biggest deficiency I'm seeing has to do with not having a "default" partition to put data that doesn't match any children. The fact that it throws an error is a concern, but it's not where I see the main problem. Where this really comes into play is when someone wants to make an existing table into a partitioned table. There's really no easy way to do this outside of making a completely brand new partition set and copying/moving the data from the old to the new. Yes there are technically ways to do this fairly seamlessly to the user of the partitioned table, but the complexity of those methods seems absurd in the face of just allowing a default partition.