Skip to content
  • Home Home Home, current page.
  • Moments Moments Moments, current page.

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
RichFelker's profile
Rich Felker
Rich Felker
Rich Felker
@RichFelker

Tweets

Rich Felker

@RichFelker

Yeah, I do @musllibc, FOSS & infosec stuff. But now is not the time for a mostly-/only-tech Twitter feed.

musl-libc.org
Joined March 2014

Tweets

  • © 2018 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • 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. Rich Felker‏ @RichFelker Mar 29

      Is this for real? If so how is Rust not a complete joke?pic.twitter.com/Zz52Hg6R9q

      5 replies 3 retweets 17 likes
    2. Peter Barfuss 𒀱‏ @bofh453 Mar 29
      Replying to @RichFelker

      okay, what else can you do in an OOM condition *that makes sense to do*, in pretty much any case?

      1 reply 0 retweets 1 like
    3. Rich Felker‏ @RichFelker Mar 29
      Replying to @bofh453

      Return (or throw, if that's your idiom) the error to the caller, leaving any mutable objects being manipulated in consistent (preferably unmodified) state.

      2 replies 0 retweets 4 likes
    4. Peter Barfuss 𒀱‏ @bofh453 Mar 29
      Replying to @RichFelker

      And 99% of the time the caller will either abort or ignore the error and SIGSEGV anyway.

      2 replies 0 retweets 0 likes
    5. Rich Felker‏ @RichFelker Mar 29
      Replying to @bofh453

      N levels back up, maybe. Unless it's stateless/contains no valuable state, or unless it's utter crap, not without first dumping a recovery file of some sort.

      1 reply 0 retweets 2 likes
    6. bounded model shaker‏ @das_kube Mar 29
      Replying to @RichFelker @bofh453

      Or you can write rust with nostd, and no allocator (bring your own). But what would you do anyway if you `vec.push(x)` and somehow there isn't enough ram? How would you signal the error in a way that makes sense to the caller of `push`?

      2 replies 0 retweets 0 likes
    7. CopperheadOS‏ @CopperheadOS Mar 30
      Replying to @das_kube @RichFelker @bofh453

      The push method could return `Ok(())` when it succeeds and `Err(x)` when it fails. Since `Result<T, U>` is marked #[must_use], it forces the caller to handle the error case. Rust as a language is well-suited to writing low-level, robust code. The non-core stdlib is the issue.

      3 replies 1 retweet 3 likes
    8. CopperheadOS‏ @CopperheadOS Mar 30
      Replying to @CopperheadOS @das_kube and

      Much more of the standard library could have been available for lower-level use. There could have been a collections and io library usable without those design decisions, etc. It was a very explicit design decision to have such lackluster low-level stdlib and ecosystem support.

      2 replies 0 retweets 1 like
    9. CopperheadOS‏ @CopperheadOS Mar 30
      Replying to @CopperheadOS @das_kube and

      Rust kept certain things like pervasive unwinding support that are ill-suited to the goals it purports to have. Unwinding is really the next thing that had to go after GC, M:N threading, segmented stacks, boxed closures, etc. There wasn't time to keep pushing for those changes.

      2 replies 0 retweets 0 likes
      Rich Felker‏ @RichFelker Mar 30
      Replying to @CopperheadOS @das_kube @bofh453

      These basically all sound like anti-features...

      5:54 AM - 30 Mar 2018
      1 reply 0 retweets 0 likes
        1. New conversation
        2. CopperheadOS‏ @CopperheadOS Mar 30
          Replying to @RichFelker @das_kube @bofh453

          It really started out as a much different language. It didn't start out trying to fill the niche of a memory safe low-level language. It was always focused on safety, but not really with the goal of avoiding performance costs, loss of control over memory layout / execution, etc.

          1 reply 0 retweets 0 likes
        3. CopperheadOS‏ @CopperheadOS Mar 30
          Replying to @CopperheadOS @RichFelker and

          To some extent, Mozilla changed the direction of the language, but to a large extent it was community pressure that fundamentally reshaped it in the year or two leading up to 1.0. It wasn't always going to be something fairly unique (i.e. a memory safe low level language).

          2 replies 0 retweets 0 likes
        4. Asa Dotzler‏ @asadotzler Mar 30
          Replying to @CopperheadOS @RichFelker and

          You said "It wasn't always going to be something fairly unique (i.e. a memory safe low level language)" Funny because that's pretty much exactly how I heard it described back at the Mozilla summit where I first learned of it in 2010, as a safe systems level language.

          1 reply 0 retweets 1 like
        5. CopperheadOS‏ @CopperheadOS Mar 30
          Replying to @asadotzler @RichFelker and

          Except 'system language' was used more like how Go was using it. Rust didn't even have borrowed pointers early on (with no plan for them). It had pervasive automatic reference counting + cycle collection with an ongoing migration to GC.

          1 reply 0 retweets 0 likes
        6. CopperheadOS‏ @CopperheadOS Mar 30
          Replying to @CopperheadOS @asadotzler and

          There was no plan to remove segmented stacks, M:N threading, etc. The plan was to move to using tracing GC, and there was at least one tracing garbage collector implemented. It was meant to be a lot more like Erlang / Go and a lot less like C and C++ than it ended up later on.

          0 replies 0 retweets 0 likes
        7. End of 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.

        Promoted Tweet

        false

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