@JayThakkar22@Ankur21689659@ZeeBusiness@AnilSinghvi_@Neha_1007 It happens consistently across multiple recommendations of yours. If you are going to tweet a '#BOOM' to celebrate a win, your data needs to account for actual retail execution slippage. Real traders get knocked out by those 'few seconds' gaps every single time.
A year ago I lost my iPhone. Recently, it suddenly appeared again on Apple’s Find My network with a recent location update from another city in Maharashtra.
Not a random guess.
Not “maybe nearby.”
An actual recent traceable location.
(1/7)
But if institutions still operate with this level of apathy, then what exactly are people supposed to rely on?
Do better @DGPMaharashtra@PCcityPolice@MahaPolice
(7/7)
@IRCTCofficial I did you guys are keep closing my ticket saying "Email id is spam" which it is not! kindly look into this ASAP. I am not able to login to my account
Now that I've got Sendable working, I can see how it simplifies async data transfer. Still, I wish there were more examples in the docs to illustrate the common pitfalls. Guess that's what Twitter's for, right?
I just spent hours wrestling with Sendable in Swift 6 and I'm still finding gotchas. Who else has tried using it with existing codable structs only to realize you need to manually implement encode and decode?
I'm starting to think that the real power of Sendable lies in its ability to simplify error handling for async data transfer. By using a single protocol, you can handle errors in a centralized way, making your code more robust and easier to maintain.