Timeline for Why do `throw` and `revert()` create different bytecodes?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 11, 2017 at 17:05 | vote | accept | SCBuergel | ||
| Jul 11, 2017 at 14:17 | answer | added | Jakub Wojciechowski | timeline score: 5 | |
| Jul 11, 2017 at 14:16 | answer | added | Rob Hitchens | timeline score: 15 | |
| Jul 11, 2017 at 14:08 | comment | added | user9402 |
Not sure if this is the reason, but the Solidity docs also say of revert(), In the future it might be possible to also include details about the error in a call to revert. And there is an open issue about completely deprecating throw: github.com/ethereum/solidity/issues/1793. It might be scaffolding for error handling down the road. Interesting question!
|
|
| Jul 11, 2017 at 14:02 | history | asked | SCBuergel | CC BY-SA 3.0 |