Robin Freyler

Currently there are the `truncate`, `zero_extend` and `sign_extend` methods and their siblings `into_*` for method chaining and `strict_*` for strict truncation and extension. Besides these a `cheap_*` sibling might be...

Require design rationals for proposals

7

We had a brief discussion about adding a requirement for rationals for WebAssembly proposals. You can read more about the existing discussion here: https://github.com/WebAssembly/reference-types/issues/71 The motivation for this is mainly...

new lint: Recommend using slice.into() to box the slice

1

### What it does Given a slice like ```rust let x: &[i32] = &[1, 2, 3, 4, ..]; ``` When users write something like ```rust let y: Box = x.iter().copied().collect();...

We lost track of the rationals and reasoning behind the `quickcheck` crate support in `fixed-hash`. This is the tracking issue for the purpose of finding out current uses of it...

Add attrs() and attrs_mut() getters to syn::Item

1

While developing certain proc macros using `syn` I found getters that return the attribute slice for a generic `syn::Item` to be missing. The implementation is straight forward and simple, however,...

Currently our event topic generation is doing lots of work that could potentially be precomputed, e.g. in case of constants. Topics computation includes computation of BLAKE-2 on some input, some...

Currently it is not possible to return anything but `Self` in ink! constructors. This is an artificial limitation created to make things a bit easier, however, technically as well as...

[Feature] Dynamic trait based contract calling

6

Since ink! 3.0-rc1 it is possible to define special trait definitions for ink! smart contract using the `#[ink::trait_definition]` proc. macro. # Motivation Defining and implementing such a trait works as...

Shared external event definitions

3

Due to ink!'s design it is not possible to share event definitions between multiple contracts since events can only be defined in the ink! module scope directly. In order to...

Separate tests from implementation in example contracts

1

Currently when viewing the source code of our example contracts they might look overwhelming at first for people that are not experienced with Rust with many hundreds of lines of...