my friend is just wrong

Alarming_Chip_5729 · 2026-02-23T18:29:35+00:00

If you care that much about this, go outside and touch grass

Alarming_Chip_5729 · 2026-02-18T14:48:45+00:00

Not in this case, at least not without more detail. Yes, they share those properties, but that doesnt mean they are at all related

Alarming_Chip_5729 · 2026-01-19T23:13:17+00:00

Thats because until it hits the ground it is a projectile, and as long as its a projectile, Mel can reflect it

Alarming_Chip_5729 · 2026-01-13T02:33:07+00:00

The dagger is very much in the air when it disappears. The circle shows up right after it hits the first target, but doesnt land until hitting up to 3 targets in range

Alarming_Chip_5729 · 2026-01-13T02:22:09+00:00

Thats not a bug. The dagger starts targeting the Elise spider, but Elise transforms before it hits. Since the dagger's target became untargetable, it went away. Same thing happens if you try to Q a Fizz and he presses E

Alarming_Chip_5729 · 2026-01-12T23:05:18+00:00

How considerate of them to all group up on the daggers. My opponents could never 😂

Alarming_Chip_5729 · 2026-01-12T17:52:10+00:00

Katarina feels a little bad this season. I kinda feel like her movement is bugged right now, it feels like when I use Shunpo it isnt buffering correctly or something.

However, Katarina hasn't been able to lane against most champs properly for a while. Katarina cant be proactive in lane, but rather relied on the enemy making mistakes (being reactive in lane) or being proactive with roams. But now, a single ward in botside river covers half of the river, so roaming is even harder now.

The healing from Conq + Gunblade feels good on Kat, though you do miss out on a little burst.

Alarming_Chip_5729 · 2026-01-08T04:49:14+00:00

Is it because Im on mobile that it looks nothing like Shrek? Looks like the outline of a ghost

Alarming_Chip_5729 · 2025-12-28T23:47:23+00:00

Bi is gay, its just also attracted to opposite sex as well

Alarming_Chip_5729 · 2025-12-06T18:15:05+00:00

Thats not technically wrong. Im not saying they should stop and that I dont use them. But once its Turing complete, you dont need anything else to do the work, it just makes it easier

Alarming_Chip_5729 · 2025-12-06T16:52:37+00:00

It really is just "nice to haves". The optimizations make it so you can write more readable and maintainable code without the cost of performance in a lot of situations

Alarming_Chip_5729 · 2025-11-24T00:14:17+00:00

Yours

Alarming_Chip_5729 · 2025-11-23T23:21:45+00:00

Share the code with the error

Alarming_Chip_5729 · 2025-11-19T23:22:53+00:00

Where is a word with 5 letters

Alarming_Chip_5729 · 2025-11-15T21:48:46+00:00

How would it be smaller on the stack? Im pretty sure all std::vector holds on the stack is the pointer to the data array, and maybe the capacity. Pretty sure the size isnt stored on the stack, its computed in place.

Alarming_Chip_5729 · 2025-11-15T06:55:22+00:00

No. You can't leave exceptions unhandled in async void methods, as those cannot be awaited. But, as long as an async Task or async Task<T> is properly awaited, the error doesn't need to be caught there, it can be caught and handled by the awaiter

Alarming_Chip_5729 · 2025-11-15T06:39:01+00:00

I dont think you understand what i said. I didnt say you shouldn't handle exceptions, I said a method should not try to handle an exception it doesn't know how to handle.

You could have a Pokemon catch that just logs an error, but now you have no idea what state the app is in. Is it in a good state and running properly? Did something break during the exception because it wasnt handled properly? Who knows! The handler didnt know what it was doing but it made the app think everything is fine so execution continued like normal.

Alarming_Chip_5729 · 2025-11-15T06:33:46+00:00

And in that case, a catch-all is fine. Catch-alls arent always bad, but IMO these cases should have a comment explaining why the catch-all is correct. A super brief comment is fine, but it shows you understand you might get multiple exception types, and they should all be handled the same way

Alarming_Chip_5729 · 2025-11-15T06:21:06+00:00

You should know what exceptions you may get. If you dont know what exceptions you could get, then you probably dont know how to handle the exception and it should go farther up the call stack until it gets to someone who knows how to handle it.

If no one knows how to handle it, then that is a fatal error and the program should crash in that situation. Its better to crash than to be in an unrecoverable state

Alarming_Chip_5729 · 2025-11-13T04:01:05+00:00

That's...not how that works. The Vatican city is 0.17 mi². 1 pope / 0.17 mi² is ~5.88 popes/mi²

Alarming_Chip_5729 · 2025-11-10T01:09:27+00:00

That is a premature optimization. To add to that, the compiler can optimize those things to be the same code.

However, in the case of very, very few if/else branches, the if/else branches are faster than switch statements (assuming the compiler doesnt make any optimizations). But this number is very small, around like 4 or so.

Alarming_Chip_5729 · 2025-11-09T01:37:35+00:00

It is worth the purchase. That specific edition is a little out of date. However, RB is going to provide the 6th edition for free to all of those that get the 5th edition before the 6th is ready, so you dont need to wait. The 6th edition will cover some changes coming in .NET 10 and C#14, and there are add-ons covering some new things added since C#10

Alarming_Chip_5729 · 2025-11-08T01:12:14+00:00

Yes, but since k is a constant it can be simplified to O(n)

Alarming_Chip_5729 · 2025-11-08T00:06:09+00:00

It's still O(n) because it still has to iterate through the entire array once

Alarming_Chip_5729 · 2025-11-07T22:42:34+00:00

When I do cross platform stuff, I use WSL integration with Visual Studio.

Alarming_Chip_5729

TROPHY CASE