Medijski sadržaj
- Tweetovi
- Tweetovi i odgovori
- Medijski sadržaj, trenutna stranica.
-
Spez: A @rustlang crate I just published that implements auto(de)ref specialization magic: https://crates.io/crates/spez/ Specialization (for macros) on stable Rust made easy!
pic.twitter.com/XvXCrGrq3K
Prikaži ovu nit -
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: https://docs.rs/assert2/ pic.twitter.com/NWHXFyToEX
Prikaži ovu nit -
"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."https://youtu.be/mzU7aIk1dGI -
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:pic.twitter.com/0ywUeR8jnq
-
Sometimes, yes. :) Still fun to play around with though. ^^pic.twitter.com/aV9xdULGWR
-
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:pic.twitter.com/YdRKZmesHv
Prikaži ovu nit -
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?pic.twitter.com/ddgRI2E3VZ
Prikaži ovu nit -
Does anyone know if this is documented behaviour? Seems to be related to the difference between calling a macro with {} and ():pic.twitter.com/SgnMtdc7R1
Prikaži ovu nit -
While trying to do something horrible in
@rustlang, 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.pic.twitter.com/c0lFdJ81IW
Prikaži ovu nit -
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! 


pic.twitter.com/lRLP8FQzGO
Prikaži ovu nit -
I started designing and selling t-shirts!
Buy my t-shirts!
More designs soon™
https://shop.spreadshirt.nl/marashop/ pic.twitter.com/K9ff279KZo
-
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.pic.twitter.com/Tr01C07MzW
Prikaži ovu nit -
Ikea invented a new unit to avoid confusion: Kilowatt hour per thousand hours, which... is exactly the same as... Watt.
pic.twitter.com/iomu7bkVva
-
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.pic.twitter.com/ds194s9fcH
-
Published a Rust crate to easily access and change individual bits in integers: https://docs.rs/intbits/ pic.twitter.com/MDcXaDqxpq
Prikaži ovu nit -
-
For comparison, the very same intersection a few years ago:pic.twitter.com/wlxwqKCxL9
-
-
Č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.