Hey #cpp, how would you refactor the code in the picture without changing its behavior?pic.twitter.com/1t982nmEsB
I'm worried that the baby thinks people can't change.
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Add this Tweet to your website by copying the code below. Learn more
Add this video to your website by copying the code below. Learn more
By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.
| Country | Code | For customers of |
|---|---|---|
| United States | 40404 | (any) |
| Canada | 21212 | (any) |
| United Kingdom | 86444 | Vodafone, Orange, 3, O2 |
| Brazil | 40404 | Nextel, TIM |
| Haiti | 40404 | Digicel, Voila |
| Ireland | 51210 | Vodafone, O2 |
| India | 53000 | Bharti Airtel, Videocon, Reliance |
| Indonesia | 89887 | AXIS, 3, Telkomsel, Indosat, XL Axiata |
| Italy | 4880804 | Wind |
| 3424486444 | Vodafone | |
| » See SMS short codes for other countries | ||
This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.
Hover over the profile pic and click the Following button to unfollow any account.
When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.
The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.
Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.
Get instant insight into what people are talking about now.
Follow more accounts to get instant updates about topics you care about.
See the latest conversations about any topic instantly.
Catch up instantly on the best stories happening as they unfold.
Hey #cpp, how would you refactor the code in the picture without changing its behavior?pic.twitter.com/1t982nmEsB
I never do return values as errors, I always use error on handle. Much more flexible, unlikely to cause resource errors, much easier for calling code to use:https://godbolt.org/z/6e7q9TPvE
I feel uncomfortable about this approach because it's very easy to forget to check if an error happened, and neither the compiler nor the type system can help you out if you do.
There is no such thing as a compiler or type system that knows if you forgot to check for an optional error. If the error is not optional, then why are you even talking about propagating it?
It wasn't clear that your original statement was about "optional errors", it sounded like you never use return values for errors generally, which I would think it is not a good idea. For an error which is "optional" I'd still value the interface of the function telling me...
It is a good idea. Any return value is optional by definition, because you are stating explicitly that the calling code may choose not to listen to it. They are obviously under no obligation to handle a return value.
I don't see it as black and white as you describe. First, there's [[nodiscard]] which signals that you ought to use the return value. Second, I often use Result<T> which forces the caller to act on it, otherwise there's no meaningful result for the caller at all.
Well, have fun.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.