What is taking `&dyn Any` and the casting it to a concrete type which was checked against a type id which came from a static array that was populated by linker hacks using the `.ctors` section?
-
-
Replying to @sgrif @mgattozzi
can we have the answer please; this is beyond my GitHub code search skills
1 reply 0 retweets 0 likes -
(1/10)xEngiNieR: Automata Retweeted Miss Dada 🏳️⚧️
(1/10)xEngiNieR: Automata added,
1 reply 0 retweets 1 like -
-
It's bad I think this is tame
1 reply 0 retweets 0 likes -
-
Replying to @Ivshti @mgattozzi
The fact that this was possible definitely made the API a lot cleaner
1 reply 0 retweets 2 likes -
I should change the annotation from `#[swirl::background_job]` to `#[really_async]`
2 replies 0 retweets 1 like -
Or maybe `#[asyncer]`? Ooh or `#[there_is_no_await]`
1 reply 0 retweets 1 like -
No gods, No await, Only async
1 reply 0 retweets 3 likes
Only async and a cron job to page whoever is on call if the jobs aren't running to completion*
-
-
Keep polling, maybe they'll finish
1 reply 0 retweets 1 like -
Replying to @mgattozzi @Ivshti
Ironically that monitor went off for the first time today and that's exactly what happened because the problem was the GitHub outage which was resolved 2 minutes after the page was sent.
1 reply 0 retweets 2 likes - 5 more replies
New conversation -
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.