alilleybrinker

8 ms·

61.
by alilleybrinker 4y ago
For a longer list of languages written in Rust, see https://github.com/alilleybrinker/langs-in-rust
62.
by alilleybrinker 5y ago
Apparently Tailscale for a long time just used a JSON file as their data storage, and moved from that to SQLite with a hot-swappable backup with Litestream [0], and hey they've done fine with that. [0]: https://securitycrypt
63.
by alilleybrinker 5y ago
Thanks for the pro-con list! The experience of... 1) build a thing because it's immediately useful for a specific use-case, 2) someone reuses it for another use-case because it's already there and saves some work, 3) times passes
64.
by alilleybrinker 5y ago
Sure, and perhaps in that context "deprecation" is the right description, but in general I've only heard that word applied to an API being in-process for removal, not as the descriptor of the final removal itself.
65.
by alilleybrinker 5y ago
Weird to see this described as a "deprecation," when really it's removed entirely.
66.
by alilleybrinker 5y ago
Calling it a “deprecation” when it’s been removed entirely seems like a misuse of the word.
67.
Good-cat: a cat that hates pipes(github.com)
2 points by alilleybrinker 5y ago|0 comments
68.
by alilleybrinker 5y ago
Years ago I wrote the official Rust FAQ [1] (now defunct). The questions were selected based on surveys of Rust users on the major Rust community spaces at the time, and a link to the FAQ was added near the top of the "Documentation&qu
69.
by alilleybrinker 5y ago
For anyone interested in languages written in Rust, here’s a list: https://github.com/alilleybrinker/langs-in-rust
70.
by alilleybrinker 5y ago
The combination of the following seems like a key problem: 1. Refusal to break ABI compatibility (so no changes to existing APIs if they cause breakage) 2. Refusal to introduce replacement APIs which can exist alongside the old ones (so you
71.
by alilleybrinker 6y ago
For anyone wanting to learn causal inference (the first item in the list), I highly recommend "Causal Inference, the Mixtape" by Scott Cunningham, a professor of economics at Baylor University. Scott has been writing this book inc
72.
Things to Try When You Can't Make a Trait Object(possiblerust.com)
1 points by alilleybrinker 6y ago|0 comments
73.
by alilleybrinker 6y ago
That is not an accurate description of events.
74.
by alilleybrinker 6y ago
That's true that in this case their plan of making the input generic wouldn't work, as it relies on the output being borrowed. The technique of reducing the size of monomorphized functions would be useful in other contexts, but no
75.
by alilleybrinker 6y ago
In cases like this, it can be useful to have the generic function call a separate, private function which does the implementation and is _not_ generic. Generic functions are monomorphized, meaning copies are generated for each concrete type
76.
by alilleybrinker 6y ago
Nicholas has been doing yeoman's work on speeding up the Rust compiler. This is the latest in a long line of contributions to tackle what has been one of Rust's most persistent problems: long compile times. * 2020-08-05: &qu