Readit NewsThis actually reminds me of my other issue with this kind of "oh we just get it for free" attitude that tends to result in overbuilding things that I also dislike in rust.
No I think people would be better off with a bespoke option parser actually.
1. `color` feature and thus the `anstream` dep is optional.
2. Even if you use it, it handles all the behaviour correctly regarding the piping and no color support, which is why it is a dependency in the first place.
Source: I am clap maintainer
Disclaimer: I built it.
This enables APIs such as `function.call_sites`, `symbol.usages`, `class.parent_classes`, and more!
And then Andrey proposed a patch in the pgsql-hackers mailing list: https://www.postgresql.org/message-id/flat/CAAhFRxitJv%3DyoG..., https://commitfest.postgresql.org/43/4388/
Everyone who can help (test, discuss, etc.) – please participate in that discussion.
The standard is not finalized yet, but there some expectations that it will be, if it happens, it would be great to have this in future Postgres 17.
I have built a postgres extension for adding ULID support which does what I described. https://github.com/pksunkara/pgx_ulid