-
All traits with unconstrained associated types have been removed as we prepare the 1.0.0 release. We are aware that this will be problematic in the short term but agreed it is the best way forward for…
-
I'd like to give a more descriptive name to this issue, but unfortunately I don't know enough about the internals of rustc to be more useful. To my uneducated eye, it seems like the Rust is choking on…
-
**EDIT: I believe my original proposal here was infeasible, so have adjusted it to a smaller (and fairly simple) change.**
[Updated Proposal](https://github.com/ziglang/zig/issues/14187#issuecommen…
mlugg updated
4 months ago
-
Sometime we need to see the file details such as size or last modified time which is what we see with folders, shortcut or any unsupported file types but with the case of supported files such as pdf, …
-
While #39959 and #111313 are discussing the same issue, in this case, it looks like there's a problem with GATs (generic associated types) or probably HRTBs (higher-rank trait bounds). Try removing th…
-
To support Notary v2 Signatures, and other supply chain artifacts like SBoMs which are associated with a target artifact, registries will need to support reference types.
## Timing
To support a …
-
Suppose you have a trait:
```
trait Foo: std::ops::Index + std::ops::Index {}
```
How do you declare a `Foo` trait object, say a `Box`? The `Output` associated types need to be specified but they …
-
`Pool` values are currently neither `Send` nor `Sync`, which precludes some interesting use cases around `rayon` and `crossbeam`.
Add support for creating a `Pool` that emits `Arc` references once …
-
A component named `NameComponent` is unnecessarily redundant, `Name` is much better.
-
As of now, all port types return `&'static` references to their contents, which allows them to be stored outside of the `run()` function, at which point the host could invalidate them (the following c…