Andrew Jones
Andrew Jones
Cannot build directly from `cargo build` or `cargo install` because of this missing header file: https://github.com/hyperledger-labs/solang/blob/c046e64db8890d0db83d65cbfd2bb0918b7ffd1e/src/linker/linker.cpp#L2 Looking at the docker image it seems this header file might be coming from...
**Early WIP** Closes #809 E.g. ```rust // Define event to be shared across contracts #[ink::event_definition] pub struct SharedEvent { arg_1: u8, #[ink(topic)] arg_2: u16, } #[ink::contract] mod contract { #[ink(storage)]...
`cargo-contract` does not currently build on Windows because of https://github.com/paritytech/cargo-contract/issues/649. This causes the Windows build of the examples step to fail. It has been temporarily commented out in https://github.com/paritytech/ink/pull/1318. Once...
Closes #825. :warning: **Breaking Change** :warning: > ## Problems >So why didn't we implement this already? The problem starts with procedural macros which are pervasive to the idea of ink!....
See https://solidity.readthedocs.io/en/develop/abi-spec.html#types Ran across this as part of https://github.com/paritytech/parity/issues/7162. The [casper contract](https://github.com/ethereum/casper/blob/master/casper/contracts/simple_casper.v.py) is written in vyper and uses the `decimal` [type](http://viper.readthedocs.io/en/latest/types.html#decimals). In the [abi](https://gist.githubusercontent.com/vbuterin/868a6213b058fb4f1fdfcf64e54f0e91/raw/33fc177da3863ec320d1ebf95816ba52ffbffbe8/casper_abi) generated by the vyper compiler it...
A WIP experiment for now just to see whether it is possible. If it is it will resolve #1428. Pulls all of the e2e testing framework and the macro into...
Follow up for #1223. See https://github.com/paritytech/ink/pull/1223#issuecomment-1248066139. In an ideal world we would be able to require the user to only import the `ink` crate. At the moment `parity-scale-codec` and `scale-info`...
**I'm submitting a ...** - [ ] Bug report - [x] Feature request - [ ] Support request - [ ] Other `ink!` events are changing in version `5.0`. See...
Follow up from https://github.com/paritytech/ink/pull/1827#issuecomment-1625583771. Currently the `Event` derive does not support generics. We should consider adding support for generic event definitions, that would allow the event definition to be used...
In order to support compatibility of `ink!` contracts with Ethereum tooling ([tracking issue](https://github.com/paritytech/polkadot-sdk/issues/111)), `ink!` will need to be able to: 1. Detect whether the contract is being invoked with Eth...