-
**Issue by [BryanQuigley](https://github.com/BryanQuigley)**
_Saturday Dec 13, 2014 at 03:46 GMT_
_For earlier discussion, see https://github.com/rust-lang/rust/issues/19801_
_This issue was labell…
-
I think this feature request has not yet its own issue although it has been discussed in e.g. #5.
I think it would be great if we could explicitly define interfaces on abstract types. By interface I …
-
This code successfully compiles even though it should not (since `String: !Copy`).
```rust
#![feature(inherent_associated_types)]
#![allow(incomplete_features)]
pub enum Ty {}
impl Ty {
…
-
### Code
```Rust
#![feature(impl_trait_in_assoc_type)]
pub trait Transaction {
type Check: 'static;
fn check(&self) -> Self::Check;
fn commit(&self, check: Self::Check);
}
pub m…
-
Should it be in the vertex / edge object itself?
What is the right syntax to access it? Can it be linked with the edge weight?
-
Generic features and the apparant lack of them in Fortran (up to the 2018 standard) are a widely discussed subject. I have written a note on the use of modules to achieve a (limted) form of genericity…
-
# Proposal
1. Use an updated Record interface that supports:
a. `Merge(rec1, rec2)` so that we can support record types that are mergeable (e.g. provider records) and not just sortable (e.g.…
-
```rust
enum A {}
impl A {
fn foo() {
use Self::*; // error: unresolved import `Self`
}
}
```
It's counterintuitive that this fails. At the very least (if it's not possible t…
-
Extracted from discussion in #7693 (such an idea has also shown up in other discussions). cc @daurnimator in particular.
There are two things which Zig is currently unable to represent cleanly:
- …
ghost updated
2 years ago
-
EDIT: ***[Current Status Update](https://github.com/rust-lang/project-error-handling/issues/3#issuecomment-1185954570)***
---
Building upon these prior issues:
- https://github.com/rust-lang/…
yaahc updated
5 months ago