Max

It is sad when projects are abandoned when maintainers run out of steam. We really need the equivalent of wills that provide for successors in such circumstances. And better ways...

Random idea for supporting maintainers: Charge $10 for opening an issue. That would have made @dtolnay $27K from this one repo (with a bunch of assumptions). Enough to pay for...

Interesting. Could you provide a small toy example to illustrate the problem? (Note: I am _not_ a maintainer but write a lot of tests that use serde. At the moment...

Interesting. Thank you for the details. > I want a compact and canonical format (like postcard, except for the canonical part). Have you considered [bincode](https://github.com/bincode-org/bincode)? It is a postcard-like format...

Thank you @guillermaster for helping and @jeemok for bringing in a maintainer. There are so many good projects out there that die because of a lack of handover. It is...

Cool, thank you for the information. I'll look at the latest `didc` and give it a spin.

Would it be an option to expose the config option via a hidden flag? Hidden in the sense that `didc --help` does not show it? That way we can test...

@chenyan-dfinity Regarding `pub`, it looks as if fields are still private for didc version 0.3.5: ``` max@sinkpad:~/dfn/nns-dapp/branches/no-pub-no-more (7:21)$ didc --version didc 0.3.5 max@sinkpad:~/dfn/nns-dapp/branches/no-pub-no-more (7:37)$ didc bind --target rs declarations/sns_ledger/sns_ledger.did |...

Purely from the technical perspective, yes, this is possible. And planned (at least, in the chain fusion signer). But when we will add subaccounts I do not know. Our roadmap...

Interesting link, @peterpeterparker . The GitHub functionality it references is documented here: https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes#configuring-automatically-generated-release-notes So it looks as if, if we were to label PRs, we could automatically populate release notes....