Charge for the gas that the contract init function spends while executing during deployment

[miloszm]

Summary

Currently, init function of a deployed contract is being executed under a gas limit regime, yet the gas spent is ignored and not charged. This may lead to an unaccounted for usage of gas, as user may effectively pay for less gas than is actually spent during deployment.

Possible solution design or implementation

Do not ignore the gas-spent result of the init function and introduce proper gas accounting for the function execution. Make sure that a contract with init function consuming a lot of gas causes one of the following:

• either OutOfGas error (charges the caller (deployer) an entire gas limit)
• or graceful exit (yet the caller (deployer) pays for the gas that has been used)