You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
-
17"exception throwing is destroying performance" - That depends on the context in which they're used, and also varies strongly from one language to another. I don't think such sweeping generalizations are very helpful.marcelm– marcelm2024-06-06 13:47:15 +00:00Commented Jun 6, 2024 at 13:47
-
3@marcelm Definitely true. While exceptions are known to be very expensive (compared to other control flows) in the C++/Java/C# class of languages, Python's exception handling is sufficiently fast to be used in the generator syntax (StopIteration), and that is so fast that it shows up in the basic underlying flow of asynchronous coroutines.Cort Ammon– Cort Ammon2024-06-06 14:45:32 +00:00Commented Jun 6, 2024 at 14:45
-
9Throwing exceptions is expensive This is an urban legend as far as the JVM is concerned. Creating exceptions with stack traces is expensive, but the unwinding operation is not.chrylis -cautiouslyoptimistic-– chrylis -cautiouslyoptimistic-2024-06-06 18:13:51 +00:00Commented Jun 6, 2024 at 18:13
-
3@chrylis-cautiouslyoptimistic- IIRC, exception handling was a lot more expensive in the very early days of Java (so the urban legend probably has a grain of truth) — but then it got optimised. And since exceptions aren't thrown very often (you're not using them for normal control flow, I hope!), it's not usually worth worrying about them; it's almost always more important to think about what makes sense for your program (what makes the code easier to understand and easier to maintain), and not think about low-level performance unless it becomes a problem.gidds– gidds2024-06-06 20:13:39 +00:00Commented Jun 6, 2024 at 20:13
-
1@Ccm Even in C++ of all languages, the current C++ Core Guidelines (FWIW) recommend the use of exceptions, even saying "We don't consider 'performance' a valid reason not to use exceptions." (source: github.com/isocpp/CppCoreGuidelines/blob/master/…)Josh Grosso– Josh Grosso2024-06-06 23:38:36 +00:00Commented Jun 6, 2024 at 23:38
|
Show 8 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you