- Sep 10, 2020
-
-
Joe Richey authored
-
Joe Richey authored
Signed-off-by:
Joe Richey <joerichey@google.com>
-
Joe Richey authored
Signed-off-by:
Joe Richey <joerichey@google.com>
-
Joe Richey authored
This makes sure we get a good compiler error if we give a bad path. Signed-off-by:
Joe Richey <joerichey@google.com>
-
Joe Richey authored
Signed-off-by:
Joe Richey <joerichey@google.com>
-
Joe Richey authored
Signed-off-by:
Joe Richey <joerichey@google.com>
-
Joe Richey authored
Signed-off-by:
Joe Richey <joerichey@google.com>
-
Joe Richey authored
Signed-off-by:
Joe Richey <joerichey@google.com>
-
Joe Richey authored
Include more links, exampales, and clarify wording Signed-off-by:
Joe Richey <joerichey@google.com>
-
Joe Richey authored
Signed-off-by:
Joe Richey <joerichey@google.com>
-
Joe Richey authored
The main things here are clarifying how fallback functionatliy works. Signed-off-by:
Joe Richey <joerichey@google.com>
-
- Sep 09, 2020
-
-
Joe Richey authored
https://github.com/rustwasm/wasm-bindgen/pull/2305 released the bugfix for wasm-bindgen. Signed-off-by:
Joe Richey <joerichey@google.com>
-
- Sep 08, 2020
-
-
Joe Richey authored
Signed-off-by:
Joe Richey <joerichey@google.com>
-
Joe Richey authored
Signed-off-by:
Joe Richey <joerichey@google.com>
-
Joe Richey authored
Cloud ABI [is now Tier 3](https://github.com/rust-lang/rust/pull/75568), so its libstd is no longer distributed with Rust. Firefox testing is also disabled due to: https://github.com/rustwasm/wasm-bindgen/issues/2261 Signed-off-by:
Joe Richey <joerichey@google.com>
-
Joe Richey authored
Also, pin the version of rustc, so that nightly updates don't break our build. This means that we can add the nightlies back into the blocking set of tests. Update the Ubuntu version to 20.04 Don't run any cargo-web tests (upstream is broken) Signed-off-by:
Joe Richey <joerichey@google.com>
-
Joe Richey authored
Signed-off-by:
Joe Richey <joerichey@google.com>
-
Joe Richey authored
Signed-off-by:
Joe Richey <joerichey@google.com>
-
- Aug 14, 2020
-
-
Joe Richey authored
Older NetBSD kernels cannot handle buffers bigger than 256 bytes, and all FreeBSD and NetBSD kernels only return up to 256 bytes per call. Signed-off-by:
Joe Richey <joerichey@google.com>
-
- Jul 22, 2020
-
-
Joe Richey authored
-
Artyom Pavlov authored
Minimum supported kernel version got bumped to 2.6.32 in rust-lang/rust#74163
-
- Jul 21, 2020
-
-
Joe Richey authored
Signed-off-by:
Joe Richey <joerichey@google.com>
-
Joe Richey authored
Right now "cargo web test" is broken due to upstream changes. We will disable stdweb tests until the stdweb project fixes things. See: https://github.com/koute/cargo-web/issues/243 Signed-off-by:
Joe Richey <joerichey@google.com>
-
- May 29, 2020
-
-
Joe Richey authored
Add back the "test-in-browser" feature. This makes it easier to manage a single file containing all of the test code. Signed-off-by:
Joe Richey <joerichey@google.com>
-
Joe Richey authored
They will be gated behind the "js" feature, as we can now do detect, at compile-time, which implementation (wasm-bindgen vs stdweb) we should use. The "js" implementation takes precedence over the "custom" implementation. This prevents issues that arise from the buggy way Cargo handles features across multiple targets. Signed-off-by:
Joe Richey <joerichey@google.com>
-
Joe Richey authored
Signed-off-by:
Joe Richey <joerichey@google.com>
-
Joe Richey authored
Right now, features are always enabled across all targets. This means that if _any_ Custom RNG is used _anywhere_ in a crate's dependancy graph on _any_ target. The "custom" feature will be active on all targets. This makes it impossible to have a bare metal target that uses "cpu" on x86_64 and a Custom RNG on aarch64. This solution also makes sure that any implementation `getrandom` itself provides cannot be overridden. Signed-off-by:
Joe Richey <joerichey@google.com>
-
- May 25, 2020
-
-
Joe Richey authored
Right now, while our implementations for stdweb and wasm-bindgen use similar APIs, they do not use similar implementations. This change: - Switches to using the same error codes for both implementations - Uses error codes that detail exactly what API is missing - Cleans up the implemetnations to make them much more readable - Consitantly use thread_local in both implementations This makes issues easier to debug and the code easier to understand. Signed-off-by:
Joe Richey <joerichey@google.com>
-
Joe Richey authored
Signed-off-by:
Joe Richey <joerichey@google.com>
-
Joe Richey authored
Signed-off-by:
Joe Richey <joerichey@google.com>
-
- Apr 28, 2020
-
-
Diggory Hardy authored
Apply #137 to 0.2 branch
-
- Apr 27, 2020
-
-
Pauan authored
-
zer0x64 authored
-
zer0x64 authored
-
Pauan authored
-
Joe Richey authored
-
Joe Richey authored
Split emscripten stuff into its own target and stop relying on cargo web to download/manage then emscripten toolchain. We can just get it ourselves. We also now run the emscripten tests. Signed-off-by:
Joe Richey <joerichey@google.com>
-
Diggory Hardy authored
travis: Allow nightly builds to fail
-
Joe Richey authored
-
Joe Richey authored
-