Mirrors/rust
1
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2026-04-27 18:57:42 +03:00
Code Issues Packages Projects Releases Wiki Activity

Minor tweak

Lindsey Kuper
2012-06-27 12:56:35 -07:00
parent 3834f5e5c8
commit df38a2bf45
1 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Proposal-for-unifying-traits-and-interfaces.md
+7 -7
@@ -93,17 +93,17 @@ impl of combine for glb {
}
```
The only other thing that we changed in this code was to change the
keyword `iface` to `trait`.
The only other thing that changed in this code was that the keyword
`iface` changed to `trait`.
## Allowing iface composability
Traits, as they appear in the literature, have a set of _provided_
methods, implementing the behavior that it provides, and a (possibly
empty) set of _required_ methods that the provided methods can be
written in terms of. For the required methods, only the names and
types are specified, not the implementation. That suggests that in
Rust, a trait's set of required methods could be specified using an
methods, implementing the behavior that a trait provides, and a
(possibly empty) set of _required_ methods that the provided methods
can be written in terms of. For the required methods, only the names
and types are specified, not the implementation. That suggests that
in Rust, a trait's set of required methods could be specified using an
iface. But if traits themselves _are_ ifaces, then that means that
ifaces can require ifaces. This goes along with the idea that traits/ifaces
should be _composable_ and _order-independent_: a trait C can extend traits A