Hacker News Reader

Something is not clear to me: can I use this in any way to generate EVM bytecode to deploy a contract? Or is this solely for use after deployment using the ABI generated by solc, etc?

I think it is the latter, but I was really hoping for the former. I welcome any improvement over solidity.

View on HN

Solidity needs formal verification much more than syntactic sugar. There's a chance solidity is already too sweet as it is.

Formal verification is needed but syntactic sugar is not inherently the problem. The problem is that there a a million gotchas because it looks high level, but isn't.

Defaulting to `storage` instead of `memory` for variables is one huge issue that can let you silently corrupt your contract.

Lack of builtin manipulation of datatypes, weird types that are cumbersome to use correctly...

I am not equipped to exhaustively lament it as a language, but it is not a pleasant experience.

Understanding Ethereum Smart Contracts | https://news.ycombinator.com/item?id=15786780

HN user jatsign shared some of his inital gotchas two weeks ago.

Sorry, this is for communicating with the already deployed contract.

Reply on news.ycombinator.com