Martin Nordholts

I don't think this issue is worth keeping open. The upstream PR has been abandoned. If upstream picks this up later, we will of course adapt, but the issue per...

This has been picked up again upstreams, see https://github.com/Enselic/cargo-public-api/pull/99 So it currently looks like this will be fixed in the coming days. Re-opening.

The upstream support will land any day now (see https://github.com/Enselic/cargo-public-api/pull/99 and referenced issue). But I have done some more thinking, and I don't think doing what this ticket is about...

I'm not entirely sure what needs to happen for this issue to be considered resolved. The current status in terms of this tool and its libraries is that out of...

Closing due to inactivity to keep he PR inbox clean, but of course feel free to re-open if you resume work on this!

Looks like I got rid of the warnings now, and this looks like a nice change to me. It has tests, CI is green, and @sharkdp even approved it already...

My 100% honest opinion is that I don't want to increase the maintenance burden of this project with Lua scripts, or anything else that is not Rust :) I do...

What you say make a lot of sense. What it boils down to for me personally is that I don't want to read or write Lua to solve problems in...

I think dependant bumps are great for bumps that are straightforward. But in this case, I'm not sure we want to split the syntax up, and what the exact implications...

For the record, here is the API diff from this PR: ``` % cargo public-api --diff-git-checkouts origin/master stabilize-syntaxes Removed items from the public API ================================= (none) Changed items in the...