What it's more likely to happen is what gets to be optimized. If something doesn't happen often, it will be slow. This is what JITs do too. DOS attacks have nothing to do with this because they don't affect correctness of the code.
-
This Tweet is unavailable.
-
-
This Tweet is unavailable.
-
Nothing in those tickets can prove that the JIT doesn’t optimize when there are exceptions. There are other bazillion of things that could be having that effect!
we cannot discuss these topics under such conditionals0 replies 0 retweets 0 likes -
This Tweet is unavailable.
-
I don’t, C2 has and can have bugs. But you’re making this statement as if it was fundamental to how it works and therefore the pure FP way should be recommended. And I think there’s nothing fundamental about throwing exceptions and having optimized code!
0 replies 0 retweets 0 likes -
This Tweet is unavailable.
-
Link from the other thread https://shipilev.net/blog/2014/exceptional-performance/ … check the conclusion section
0 replies 0 retweets 1 like -
This Tweet is unavailable.
-
I'm not sure I'm understanding this correctly... wrapping a result in Either adds a cost (potentially optimised) to every single successful case. Throwing an exception adds a larger cost to every single failure.
2 replies 0 retweets 0 likes
But if those exceptions are terminal, or at least short-circuiting in some way, it seems (assuming the JSON example) like it would be impossible to have enough exceptions thrown in a DOS attack to outweigh the penalty of the additional allocations for Either.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.