Skip to content

typo fix #40

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Feb 15, 2019
Merged

typo fix #40

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion _posts/2018-12-06-reflecting-on-rust-and-wasm-in-2018.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ Rust 2018 shipped.
### Goal: ☑ Zero-Cost JavaScript Interoperation

Rust enables fast *and* expressive code by leveraging zero-cost abstractions. We
wanted to apply this principal to our whole JS interop infrastructure. Yes, you
wanted to apply this principle to our whole JS interop infrastructure. Yes, you
can write your own boilerplate to pass DOM nodes to Rust-generated wasm, but you
shouldn't have to, and the provided infrastructure should be as fast as if you
*did* hand-code it. If you call IndexedDB APIs, that shouldn't bloat your
Expand Down