https://twitter.com/jeune_afrique/status/1500886979944275969

https://twitter.com/jeune_afrique/status/1500886979944275969

Most recents (7)

The war in #Ukraine will bring a sea change in the #Libyan crisis

#JeuneAfrique kindly included a few of my thoughts on why observers really ought to brace for substantial side effects, not just minor ones.

[ thread on the #Russia facet of the #Libya reality c. 2022 ]

https://twitter.com/jeune_afrique/status/1500886979944275969

Since the Feb. 24 launch of the invasion of Ukraine, apart from lots of unfounded speculation, there’s been not a shred of evidence to suggest any number of #Russian fighters have left Libya.

In fact, over the last several months, the number of Russians in #Brak has increased.

Historically, 1 of the top reasons #Russia has acquired a clandestine #military presence in #Libya is the fact that it’s key strategic territory on #NATO’s southern flank. The #Ukraine crisis of 2014 deepened the Kremlin’s perception of NATO as hostile to Russia’s core interests.

Read 13 tweets

Anson Horton

@AnsonHorton

1/ At the time that we shipped VS 2002, it was common to release several 'service packs' over the course of months or years afterwards. These service packs contained a large number of bug fixes that addressed issues that were discovered after we released. In comparison to today,

2/ the pace of releasing was glacial. I am much happier with the velocity at which we can ship updates now (though admittedly, I know some folks wish we didn't ship quite so often). Regardless, the next release after VS 2002 was originally intended to be a service pack. However,

3/ after some development, it became clear that the service pack was growing past simple bug fixes. Most notably, the release was set to align with the release of the .NET compact framework (anyone remember the codename for this? :-), and we wanted VS to have good support for

Read 14 tweets

Joe Masilotti

@joemasilotti

XCTest tips and tricks that can level up your Swift testing.

🧵👇

1. Use XCTUnwrap instead of force wrapping optionals

Force unwrapping a nil will cause the test suite to completely crash, meaning no output or reporting. XCTUnwrap provides a nice failure message and fails the test.

2. Set continueAfterFailure to false

If you have multiple assertions in a test they might increase in specificity. The first asserts the size of the array and the second assets the first element. You don't want to run the second if the first fails, it's just noise.

Read 13 tweets

Shafik Yaghmour

@shafikyaghmour

#102 The result of an infinite recursion in template instantiation is undefined behavior: eel.is/c++draft/temp.…

godbolt: godbolt.org/z/jh6bsr

#103 Referring to any non-static member or base class of an object in the handler for a function-try-block of a
constructor or destructor for that object results in undefined behavior: eel.is/c++draft/excep…

godbolt: godbolt.org/z/6Yzvvc

#104 If the token defined is generated as a result of this replacement process or use of
the defined unary operator does not match one of the two specified forms prior to macro replacement, the
behavior is undefined: eel.is/c++draft/cpp.c…

godbolt: godbolt.org/z/xrdfT4

Read 20 tweets

報導者 The Reporter

@tw_reporter_org