Bernhard Mueller

I reverted the merge of Korean translations by @James-Lim as it broke some stuff on the page. When we have a solution for multi-lang we can incorporate them again. The...

Yep, to me the title "Requirement Violation" would indicate that requirement violations are always "wrong". However, the way I understand it, `require(`) is the recommended way to catch invalid inputs,...

For clarification: ``` pragma solidity ^0.4.25; contract Bar { Foo private f = new Foo(); function doubleBaz() public view returns (int256) { return 2 * f.baz(0); } } contract Foo...

Hmm, yeah in a sense requirement violations are always "wrong" when happening during runtime, but the use of a `require` statement by the programmer for catching a possible violation isn't...

> And introduce a compiler flag, which includes them in the generated bytecode. +1

Hey @xyliang01, the officially supported way of doing this is: - Initialise the state you want in Ganache - Run `myth analyze --rpc ganache -a ` This will initialise bytecode,...

That's a great idea! Ideally, we'd integrate Mythril with EthPM so that all packages in the registry get analyzed automatically. This would also make for a great analysis-at-scale project.

I suspect that this is indirectly addressed by #513?

@ytrezq #1268 introduces this feature, would you like to test it?

Yeah, that sounds good.