| Tweetovi |
|
Benjamin Brittain
@Brittain_Ben
|
3 h |
|
Inversely correlated 😈
|
||
|
|
||
|
Benjamin Brittain
@Brittain_Ben
|
2. velj |
|
The author of pico-args updated their table!
github.com/RazrFalcon/pic…
|
||
|
|
||
|
Benjamin Brittain
@Brittain_Ben
|
1. velj |
|
We had a large corpus of binaries. I'll look for the data next week
|
||
|
|
||
|
Benjamin Brittain
@Brittain_Ben
|
31. sij |
|
This was written 6+ months ago (I only now just got around to making it stand-alone). I don't remember the numbers but it was *significant*
|
||
|
|
||
|
Benjamin Brittain
@Brittain_Ben
|
31. sij |
|
I pulled a Rust library out of Fuchsia into a stand-alone crate.
If you want an ergonomic derive based argument parser that also cares about binary size, check it out!
Github.com/Google/argh
|
||
|
|
||
| Benjamin Brittain proslijedio/la je tweet | ||
|
Alison Macrina
@flexlibris
|
31. sij |
|
Millennials are actually a two-part generation, Late and Early, split along what could be called the My Chemical Romance divide.
|
||
|
|
||
|
Benjamin Brittain
@Brittain_Ben
|
30. sij |
|
Binary size & battery on mobile
|
||
|
|
||
|
Benjamin Brittain
@Brittain_Ben
|
30. sij |
|
You might not even have worse performance. Caches can work with code like this better in some circumstances
|
||
|
|
||
|
Benjamin Brittain
@Brittain_Ben
|
30. sij |
|
Yeah, this still isn't sounding right unfortunately. 😟
|
||
|
|
||
|
Benjamin Brittain
@Brittain_Ben
|
30. sij |
|
Unfortunately I can't use hyper or libcurl.
I also can't use async-std
|
||
|
|
||
|
Benjamin Brittain
@Brittain_Ben
|
29. sij |
|
Something about this exhange made me breakdown in laughter. This is absolutely ludicrous, horrible, and amazing.
reddit.com/r/rust/comment…
|
||
|
|
||
|
Benjamin Brittain
@Brittain_Ben
|
28. sij |
|
Nearly every day I find another reason why all build systems should be hermetic
|
||
|
|
||
|
Benjamin Brittain
@Brittain_Ben
|
28. sij |
|
The last one isn't a winnable political battle in most organizations unfortunately. Hard to justify that cost (and I don't even know which side I'd fall on)
I love that you are proactively looking for feedback though!
|
||
|
|
||
|
Benjamin Brittain
@Brittain_Ben
|
28. sij |
|
Python has enough overhead to begin with. The other problem is that types really shine in large codebases and you'll almost certainly have a requirement on Cpython extensions.
|
||
|
|
||
|
Benjamin Brittain
@Brittain_Ben
|
28. sij |
|
or, resugaring the closure: play.rust-lang.org/?version=night…
|
||
|
|
||
|
Benjamin Brittain
@Brittain_Ben
|
28. sij |
|
I mean, you won't be able to express them properly, even though you could write them out.
If you remove the references:
play.rust-lang.org/?version=night…
|
||
|
|
||
|
Benjamin Brittain
@Brittain_Ben
|
28. sij |
|
You can express this, but you are gonna run into higher rank trait bound problems. The lifetimes in that playground don't work
|
||
|
|
||
|
Benjamin Brittain
@Brittain_Ben
|
28. sij |
|
Is this what you were trying to do?
play.rust-lang.org/?version=night…
|
||
|
|
||
|
Benjamin Brittain
@Brittain_Ben
|
27. sij |
|
Rust has many flaws, but I'm struggling to see the boilerplate in this context. You say "A Fn, that returns a Future"
play.rust-lang.org/?version=night…
|
||
|
|
||
|
Benjamin Brittain
@Brittain_Ben
|
27. sij |
|
♥️
|
||
|
|
||