Robin Freyler

> A promising [experiment](https://github.com/paritytech/ink/compare/aj-events-refs?expand=1): I managed to get `7.9K` (down from `11.0K`) from the latest `master` with making everything a reference: > > ``` > /// Event emitted when a...

We are currently working to make ink! trait definitions really usable and afterwards this feature is going to be very important in my opinion. The ability to define ink! traits...

Let us first get non-generic traits right and then we can tackle making them generic or adding similar features that will help with library-like smart contracts that are urgently needed.

This is going to be fixed in https://github.com/paritytech/ink/pull/665 where all ink! trait definitions are generic over an ink! contract environment.

What is the difference from this feature to chain extensions that allow for the same functionality?

I am not sure if this is entirely bad since this is an artifact of the actual Rust code itself. For example: ```rust /// Foo. fn foo() {} ``` Will...

> I agree. I think a valid condition would be to only remove the whitespace if every item in the docs Array starts with a whitespace. Yes but just remove...

# Off-chain Redesign ## Problems With Old Design - Is the notion of an execution context actually a good idea? - Must always define "big object" and cannot set just...

Indeed implementing this will be very difficult. I personally am out of ideas how to properly implement this given our current off-chain engine architectures. @cmichi do you have ideas? @KaiserKarel...

> [...] Unfortunately, most of my contracts use other contracts [...] Yep, this is kind of expected and normal with more complex smart contracts. The off-chain environments that have been...