Mara Bos

@m_ou_se

Rust dev, Electronics engineer, Founder/CTO of Fusion Engineering, C++ geek, Maintainer of , Ex-Googler, Open-source fan, Polyamorous, Lesbian, She/her

Delft, Nederland
Vrijeme pridruživanja: travanj 2009.

Medijski sadržaj

  1. 12. sij

    ✨ 🆕 ✨ Spez: A crate I just published that implements auto(de)ref specialization magic: Specialization (for macros) on stable Rust made easy! 🎉

    Prikaži ovu nit
  2. 10. sij

    A friend of mine just published the `assert2` Rust crate: assert!() and check!() macros that show the left and right hand sides of ==, <, etc. separately when they fail. Check it out:

    Prikaži ovu nit
  3. 3. sij

    🎶 "And the images that fucked ya. Were a patriarchal structure. And you never will surrender. To a narrow view of gender. And I swear there’ll come a day. When you won’t worry what they say."

  4. 20. pro 2019.
    Odgovor korisniku/ci

    Ijsselmeer feels like a clumsy typo to me. ^^ We learn IJ as a single letter. Here's IJ taking up a single space in a monospace font, which looks way better than a separate I and J to me:

  5. 30. stu 2019.
    Odgovor korisnicima

    Sometimes, yes. :) Still fun to play around with though. ^^

  6. 30. stu 2019.

    By (ab)using this behaviour, a macro can do different things depending on the context in appears in. (By expanding to an expression which behaves differently based on the deduced type.) For example, the inline-python crate could use this to optionally capture/use Python context:

    Prikaži ovu nit
  7. 30. stu 2019.

    So, Rustc doesn't know what type to pick for `A.into()` when it appears by itself as a statement, but if it was the result of a macro expansion (with `{}` and an implied `;`), it infers the expression must result in (). Is this supposed to happen? Can I rely on this behaviour?

    Prikaži ovu nit
  8. 30. stu 2019.

    Does anyone know if this is documented behaviour? Seems to be related to the difference between calling a macro with {} and ():

    Prikaži ovu nit
  9. 30. stu 2019.

    While trying to do something horrible in , found this interesting subtle difference between a macro expansion being interpreted as an expression or a statement: What makes it even more confusing, is that both produce the exact same output with rustc --pretty=expanded.

    Prikaži ovu nit
  10. 30. stu 2019.

    A few months ago, I asked the city councel of my hometown Delft to consider making a rainbow crossing. 🏳️‍🌈 Today, I received their reply saying that in response to my letter, they're going to turn the bridge right next to the main train staion into a rainbow bridge! 🏳️‍🌈🎉😍🌈

    Prikaži ovu nit
  11. 29. stu 2019.

    I started designing and selling t-shirts! 👕 Buy my t-shirts! 💶 More designs soon™

  12. 9. lis 2019.

    So, rustc doesn't inline functions across crates even if they are trivial, when they are not generic and have no #[inline]. Turns out the popular embedded crates all have quite a few trivial functions (returning consts etc.) that still ended up as explicit calls in the binaries.

    Prikaži ovu nit
  13. 5. lis 2019.
    Odgovor korisniku/ci

    Ikea invented a new unit to avoid confusion: Kilowatt hour per thousand hours, which... is exactly the same as... Watt. 😆

  14. 4. lis 2019.
    Odgovor korisnicima

    Hm, just realized that doing it in reverse order is more efficient. Then it doesn't copy the whitespace at the end when cutting the whitespace at the beginning off.

  15. 27. ruj 2019.

    Published a Rust crate to easily access and change individual bits in integers:

    Prikaži ovu nit
  16. 16. ruj 2019.
    Odgovor korisniku/ci

    Hospital: Here's your trans plant.

  17. 30. srp 2019.
    Odgovor korisnicima
  18. 30. srp 2019.
    Odgovor korisnicima

    For comparison, the very same intersection a few years ago:

  19. 17. srp 2019.
    Odgovor korisniku/ci

    This inspired me to do some experimenting. ^^

  20. 9. srp 2019.
    Odgovor korisnicima

    I've only seen this once in Delft: :)

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·