Alexander Regueiro
Alexander Regueiro
@ilike2burnthing Just tested, and seems to work fine for me. (M1 Max MBP)
@ilike2burnthing Sorry, saw the tag and read your comment too hastily. But yes, at least we can confirm this.
@plk Thanks for your reply. That's good to know. I am trying to refresh my memory as to my exact use case (since it was so long ago), but I...
Actually, this seems to be happening on DB close, upon further investigation.
@ehuss I've been reviewing @dmarcuse's efforts on this for a while now (she's a new contributor), and would like to say it's in a great state to get some official...
> Instead I would propose a new per-target `features` (name to be bikeshedded) key that lists the features that this target enables. I personally don't like the indirectness of this...
@alexcrichton Sounds like a nice approach that doesn't lose too much in honesty. I guess it all depends how painful it would end up being to update the index, which...
From my perspective, having bin targets enabling features would be something of an abuse of the purpose of features. As far as I know (and intuitively), they're meant to be...
Whatever viewpoint one takes, I don't like being stuck in a halfway house. Either we should move towards an enforced no-binaries-per-crate (away from the status quo) or improve the ergonomics...
I'm for this. It arguably reduces the semantic complexity of the language, and improves consistency, especially with let-chaining coming in. Has @rust-lang/libs thought of bundling the `is!` macro with the...