Nipunn Koorapati

Hello sentry! I believe this was incorrectly closed by the bot. Could someone from the sentry team take a look? Perhaps @ArthurKnaus could help (just looking at history in this...

Thanks @stephanie-anderson - let me know if there's anything I can do from my side. I can rebase to resolve conflicts.

I'm not sufficiently familiar with the buf ecosystem to feel comfortable maintaining this. However, I'd be happy to include links to other solutions in the README (PRs welcome) If there's...

Mypy itself uses comment-style type annotations for all < python 3.6 code. Grammar was introduced in python 3.6 https://mypy.readthedocs.io/en/stable/cheat_sheet_py3.html (search for "type comment") There are standard comment style type annotations...

If we assume that features are additive (as intended), then the innermost crate could be compiled once with the union of all features. Additive features are a bit of a...

For what it's worth, we've done that exact trick with the parallel feature of the gcc crate. It does happen, but the workaround is ok. On Wed, Sep 6, 2017...

I would be in support of `cargo build --all` building the same dependency multiple times rather than resolving a feature union. This would be equivalent of running `cargo build` in...

We've had to fork some deps to unify feature selection to work around this issue. It's definitely not sustainable for us, but not urgent yet. --Nipunn On Sat, Oct 14,...

Here's an example of a problem we had to work around https://github.com/rust-lang/cargo/issues/3620#issuecomment-326462000 In that particular case, either and itertools were both present in our workspace. We ended up internally forking...

^ we have the same issue with `winapi` in particular. We worked around it by autogenerating our `Cargo.toml` to always specify the exact union of winapi features which we require...