You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
Made to run natively on all modern operating systems and browsers, Ruffle brings Flash content back to life with no extra fuss. Safe to use— Using the guarantees of Rust and WASM, we avoid the security pitfalls Flash was known for. Easy to install— Whether you’re a user or a website owner, we’ve made it as easy as possible to get up and running.
⚠️ This project is currently not actively maintained. Most of the other maintainers have moved on to other WebAssembly related projects. This project could definitely still be useful to anyone who wants to write a custom Kubelet and its sister project Krator is a state machine-based solution for writing Kubernetes controllers/operators in Rust. If anyone is interested in maintaining these projects
Hey everyone. I’m a bit obsessed with web assembly, so I thought i’d tried to write some semi-higher quality information about what I’ve learned. Some months ago I just started reading the web assembly spec and poking around at bytes. It all started as just a fundamental question “what’s even in here?” What makes the magic of all this “faster than JavaScript” stuff work? It ended up being pretty f
impl トレイト名 は Rust で存在型を扱うのに使える 。しかし、以下はコンパイルが通らない。 use std::fmt::Display; fn f<T>(t: T) -> impl Display where T: Display, { t } fn main() { let mut s = f(""); s = f(s); } Compiling playground v0.0.1 (/playground) error[E0308]: mismatched types --> src/lib.rs:12:11 | 12 | s = f(s); | ^ expected `&str`, found opaque type | = note: expected reference `&str` found opaque type `impl std::fmt::Display`
Fuzzing or fuzz testing is an automated testing technique that involves providing invalid, unexpected, or random data as inputs to a program to find bugs that would be otherwise hard to find with manual generated input. — Wikipedia In the last months I’ve been working developing fuzzing targets to find bugs and create patches for the Wasmer WebAssembly runtime. In this post we will learn what is f
Jan 17 2020 actix-web is dead. This situation is bad, from all sides. When Rust was a tiny, tiny community, I thought to myself, “wow, I wonder how long this will last? Probably 1.0 will kill it.” Sort of playing off of Eternal September, I assumed that over time, the community would grow, and we’d encounter problems. Today is the first day where I say to myself, okay, has that happened? This stor
hkt.rs 0$�� �� use std::rc::Rc; trait HKT<U> { type C; // Current type type T; // Type with C swapped with U } macro_rules! derive_hkt { ($t:ident) => { impl<T, U> HKT<U> for $t<T> { type C = T; type T = $t<U>; } } } derive_hkt!(Vec); derive_hkt!(Option); derive_hkt!(Box); derive_hkt!(Rc); trait Functor<U>: HKT<U> { fn map<F>(&self, f: F) -> Self::T where F: Fn(&Self::C) -> U; } impl<T, U> Funct
Rustの特徴のひとつは、所有権(ownership)・移動(move)・借用(borrow)の概念です。これらがコンパイル時に厳格にチェックされることにより、古くから未定義挙動でプログラマを悩ませてきたダングリングポインタなどの問題がなくなり、メモリ安全性がもたらされます。 しかし一方で、自分で多少複雑なデータ構造を定義しようとする場合にはコンパイルを通すだけでもかなりの知識・力量が要求されます。 この(不定期)連載では、 Rustではじめるデータ構造とアルゴリズム と題し、プログラミングコンテストなどでよく見かける基礎的なデータ構造とアルゴリズムを、できるだけシンプルにRustで実装していきます。 &, &mut, Box, Rc, Cell, RefCell などの使い分けや、なぜそれを使う必要があるかの解説を、実例を通して行います。 第1回は、最もシンプルな木構造である 二分木 を
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く