4

Should we merge "errors" into "exceptions" tags? suggested that is too general.

Since "out-of-gas" is the most common exception/error in Ethereum, should we retag/rename to ? It fits all questions currently tagged with .

  • Bad JUMPDEST exceptions are also quite common – Tjaden Hess Jan 30 '16 at 2:36
  • But aren't most of those "Bad JUMPDEST" due to out-of-gas instead of handwritten bytecode that specified an invalid jumpdest ? – eth Jan 30 '16 at 6:55
  • 1
    Yes, but it would be confusing for someone experiencing a JUPDEST error to tag their post with a GAS exception. Just using the "exception" tag seems more general and intuitive to me. – Tjaden Hess Jan 30 '16 at 6:57
  • Agreed with Tjaden, maybe we just want to add an out-of-gas tag instead of using it as a replacement. – Joël Feb 1 '16 at 0:23
  • Agree with having tags for specific exceptions. Technically these are halting-exceptions and I think it's appropriate to have multiple tags because there can also be a solidity-exception (which is different). – nessence Feb 14 '16 at 2:01
2

Yes, this works very well for all 4 questions being tagged with

2

Please use both tags. The error message in the geth logfile is "Out of Gas". New devs don't always know they are related. As a matter of fact, I recall finding out the hard way that throw in solidity uses up all available gas.

  • Agree if both can fit. I tried adding back exceptions tag to your question, but not sure which tag should be booted out to make room for it... – eth Feb 9 '16 at 18:55
0

I would like to suggest using out-of-gas and evm-exception. Solidity has exceptions too so "exception" maybe too generic. "exception" isn't so bad if its alongside one of the other tags.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .