Robin Freyler

Results 177 issues of Robin Freyler

We currently are lacking a CI job in our GitHub Actions CI for running our testsuite using the [miri](https://www.google.com/search?hl=en&q=rustlang%20miri) tool. This tool is excellent for checking `unsafe` Rust code soundness...

enhancement
help wanted
wasmi-v1

After https://github.com/paritytech/wasmi/issues/304 has been implemented it would be nice to have benchmarks run automatically for every PR and PR update similar to how it is already done with test coverage...

enhancement
help wanted

## Current State & Problem Currently users of `wasmparser` have to instantiate a [`FuncValidator`](https://docs.rs/wasmparser/0.88.0/wasmparser/struct.FuncValidator.html) for every Wasm function in a Wasm module that they want to validate. For larger Wasm...

With https://github.com/bytecodealliance/wasm-tools/pull/697 merged it is possible to remove the [`Operator`](https://docs.rs/wasmparser/0.88.0/wasmparser/enum.Operator.html) type from the `wasmparser` crate. The new [`VisitOperator`](https://github.com/bytecodealliance/wasm-tools/blob/63f8ab39d93925fd3463236814128de23fc3ac5e/crates/wasmparser/src/readers/core/operators.rs#L1193) trait allows to parse and validate Wasm without the need for matching...

At the moment the new `VisitOperator` trait requires users to implement each and every of the over 500 variants. This quickly becomes a mundane task, especially if there are only...

wasmparser

## tl;dr We might have a discoverability problem with all the Wasm proposals and extensions implemented in this crate. ## Problem When working with the very low level and generic...

wasmparser

Currently the `Operator` enum has a lifetime attached which makes it a bit harder to work with in some contexts. The only reason for this is its `BrTable { table:...

wasmparser

Wasmtime has implemented differential fuzzing against the `wasmi` interpreter. However, the currently supported `wasmi` version is very old and outdated. #### Benefits The `wasmi` interpreter has since evolved quite a...

fuzzing

Today I found out that tokei's reported lines of code for my repository seemed to explode. The reason for this was that tokei (incorrectly) counted links (symbolic-links and hard-links) as...

enhancement

## Problem Description & Current State Currently all ink! items are always defined in a single file. The reason for this is that we only allow defining ink! definitions that...

B-enhancement
A-ink_lang