Skip to content
By using Twitter’s services you agree to our Cookies Use. We and our partners operate globally and use cookies, including for analytics, personalisation, and ads.

This is the legacy version of twitter.com. We will be shutting it down on June 1, 2020. Please switch to a supported browser, or disable the extension which masks your browser. You can see a list of supported browsers in our Help Center.

  • Home Home Home, current page.
  • About

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @
  • Language: English
    • Bahasa Indonesia
    • Bahasa Melayu
    • Català
    • Čeština
    • Dansk
    • Deutsch
    • English UK
    • Español
    • Filipino
    • Français
    • Hrvatski
    • Italiano
    • Magyar
    • Nederlands
    • Norsk
    • Polski
    • Português
    • Română
    • Slovenčina
    • Suomi
    • Svenska
    • Tiếng Việt
    • Türkçe
    • Ελληνικά
    • Български език
    • Русский
    • Српски
    • Українська мова
    • עִבְרִית
    • العربية
    • فارسی
    • मराठी
    • हिन्दी
    • বাংলা
    • ગુજરાતી
    • தமிழ்
    • ಕನ್ನಡ
    • ภาษาไทย
    • 한국어
    • 日本語
    • 简体中文
    • 繁體中文
  • Have an account? Log in
    Have an account?
    · Forgot password?

    New to Twitter?
    Sign up
stjepang's profile
Stjepan Glavina
Stjepan Glavina
Stjepan Glavina
@stjepang

Tweets

Stjepan Glavina

@stjepang

async runtimes and concurrency primitives in @rustlang he/they (available for hire)

Berlin, Germany
stjepang.github.io
Joined October 2009

Tweets

  • © 2020 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • Imprint
  • Cookies
  • Ads info
Dismiss
Previous
Next

Go to a person's profile

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @

Promote this Tweet

Block

  • Tweet with a location

    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

    Your lists

    Create a new list


    Under 100 characters, optional

    Privacy

    Copy link to Tweet

    Embed this Tweet

    Embed this Video

    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

    Hmm, there was a problem reaching the server.

    By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.

    Preview

    Why you're seeing this ad

    Log in to Twitter

    · Forgot password?
    Don't have an account? Sign up »

    Sign up for Twitter

    Not on Twitter? Sign up, tune into the things you care about, and get updates as they happen.

    Sign up
    Have an account? Log in »

    Two-way (sending and receiving) short codes:

    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

    Confirmation

     

    Welcome home!

    This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.

    Tweets not working for you?

    Hover over the profile pic and click the Following button to unfollow any account.

    Say a lot with a little

    When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.

    Spread the word

    The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.

    Join the conversation

    Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.

    Learn the latest

    Get instant insight into what people are talking about now.

    Get more of what you love

    Follow more accounts to get instant updates about topics you care about.

    Find what's happening

    See the latest conversations about any topic instantly.

    Never miss a Moment

    Catch up instantly on the best stories happening as they unfold.

    1. Lucretiel  🦀‏ @Lucretiel May 10
      • Report Tweet
      • Report NetzDG Violation
      Replying to @techpractical

      It's probably going to be heavily based on smol. I was inspired by @stjepang's simple and straightforward design and wanted to see if I could carry it even farther forward, getting rid of globals entirely.

      1 reply 0 retweets 2 likes
    2. Stjepan Glavina‏ @stjepang May 10
      • Report Tweet
      • Report NetzDG Violation
      Replying to @Lucretiel @techpractical

      Are you going to use thread-locals or getting rid of them also? I'm considering removing the global executor from smol so the only two globals would be: 1. the reactor 2. the blocking pool

      1 reply 0 retweets 0 likes
    3. Lucretiel  🦀‏ @Lucretiel May 10
      • Report Tweet
      • Report NetzDG Violation
      Replying to @stjepang @techpractical

      Ideally no thread-locals, but we'll see what's possible. My ideal design has all the relevant resources (reactor, pool) live high in the stack (near main) and passed by reference parameter down into the actual async code, but I'm not sure if the lifetimes can be made to work

      1 reply 0 retweets 0 likes
    4. Stjepan Glavina‏ @stjepang May 10
      • Report Tweet
      • Report NetzDG Violation
      Replying to @Lucretiel @techpractical

      I see - my hunch is that Arcs will be needed to make this practical, but would love to be proven wrong! Btw, I wonder why you want to eliminate all globals?

      3 replies 0 retweets 2 likes
    5. Lucretiel  🦀‏ @Lucretiel May 10
      • Report Tweet
      • Report NetzDG Violation
      Replying to @stjepang @techpractical

      I guess I should elaborate that I'm not opposed to globals in general, just to interfaces that leak the global-ness. I think futures-timer is a great example of this done well; it uses a global background thread to manage the list of queued timers and send wakeups as needed.

      1 reply 0 retweets 0 likes
    6. Lucretiel  🦀‏ @Lucretiel May 10
      • Report Tweet
      • Report NetzDG Violation
      Replying to @Lucretiel @stjepang @techpractical

      This is great because the interface is just "create a future that completes at a certain time / after a certain timeout". It's seamlessly compatible with any runtime, and now you can create timeouting futures through simple composition via Select.

      1 reply 0 retweets 0 likes
    7. Stjepan Glavina‏ @stjepang May 10
      • Report Tweet
      • Report NetzDG Violation
      Replying to @Lucretiel @techpractical

      Makes sense, although I'm not sure I understood completely. Do you have examples of interfaces that leak globalness? Do you consider async-std's concept of global runtime "good" or "bad"?

      1 reply 0 retweets 0 likes
    8. Lucretiel  🦀‏ @Lucretiel May 10
      • Report Tweet
      • Report NetzDG Violation
      Replying to @stjepang @techpractical

      So, suppose you had a server that consumed an API. Suppose that for whatever reason, you want to use async-std-based library for handling incoming connections, but a tokio-based library for handling outgoing connections.

      1 reply 0 retweets 0 likes
    9. Lucretiel  🦀‏ @Lucretiel May 10
      • Report Tweet
      • Report NetzDG Violation
      Replying to @Lucretiel @stjepang @techpractical

      My understanding is that this doesn't work well, because they have their own reactors and both want to take control of `main` and want to control when blocking (ie, waiting for OS events) actually occurs.

      1 reply 0 retweets 1 like
    10. Lucretiel  🦀‏ @Lucretiel May 10
      • Report Tweet
      • Report NetzDG Violation
      Replying to @Lucretiel @stjepang @techpractical

      In theory, there's no reason it couldn't work, though. You'd pay an efficiency penalty, but there's nothing preventing an application from having more than one epoll set up, and having different threads wait on them separately. That's what I mean by leaky globalness.

      1 reply 0 retweets 1 like
      Stjepan Glavina‏ @stjepang May 10
      • Report Tweet
      • Report NetzDG Violation
      Replying to @Lucretiel @techpractical

      I see - so by leaky globalness you mean "i need to do extra steps to make things work"? So in that sense tokio is leaking, but async-std isn't - is my understanding correct?

      1:50 PM - 10 May 2020
      0 replies 0 retweets 0 likes

      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.

        Promoted Tweet

        false

        • © 2020 Twitter
        • About
        • Help Center
        • Terms
        • Privacy policy
        • Imprint
        • Cookies
        • Ads info