Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFC: Coercible and HasPrefix for Zero Cost Coercions #91

Closed
wants to merge 3 commits into from
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Fixed typo
  • Loading branch information
Jonathan S committed May 25, 2014
commit 71844868f6342761db8f23e1dbf152a2870b5d61
4 changes: 2 additions & 2 deletions active/0000-zero-cost-coercions.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,8 +62,8 @@ any two types where the target type "is a proper subtype of" the input type. Not
is never a virtual call, as it is not a method of `Coercible`: `Coercible<T>` doesn't have a
vtable, and is considered a built-in "kind" alongside `Copy`, `Send`, etc.

Where single inheritance and subtyping conflate many different ideas, among them transparenta
ccess to superstruct fields, zero-cost conversion from sub- to supertypes, and these conversions
Where single inheritance and subtyping conflate many different ideas, among them transparent
access to superstruct fields, zero-cost conversion from sub- to supertypes, and these conversions
being implicit/automatic, `Coercible` captures and exposes only the thing which is truly important:
the zero-cost conversions, and for a much wider range of scenarios.

Expand Down