llogiq

9 ms·

31.
Rust 2021 – Ethical Development(llogiq.github.io)
4 points by llogiq 6y ago|1 comments
32.
by llogiq 6y ago
We should be able to write a MIR lint that gives us linear types wherever we want them. I hear they are most useful with unsafe code.
33.
How to Write Crap Rust Code(blog.logrocket.com)
1 points by llogiq 6y ago|0 comments
34.
Aleph-alpha-tokenizers: Faster NLP tokenizing(aleph-alpha.de)
2 points by llogiq 6y ago|0 comments
35.
by llogiq 6y ago
Then perhaps the bstr crate ( https://docs.rs/bstr/0.2.12/bstr ) might be what you want.
36.
by llogiq 7y ago
What arena types do you use? If you need to store pointers and want to conserve a bit of memory, perhaps my compact_arena crate can help you.
37.
by llogiq 7y ago
> Sometimes it seems like Rust afficionados think that buffer overflows etc. are the main kind of bugs. Have you looked at the CVE stats of the last decade recently? Memory errors make up around 3/4 of that. Even if Rust would make
38.
Blog: Rust Faster – SIMD Edition(llogiq.github.io)
3 points by llogiq 8y ago|0 comments
39.
Llogiq on stuff – A Self-ish Bug(llogiq.github.io)
1 points by llogiq 8y ago|0 comments
40.
by llogiq 8y ago
One thing the linked ripgrep post doesn't tell you is that line counting is also done with SIMD since it started using bytecount ( https://github.com/llogiq/bytecount ) some months ago, which sped up some workloads
41.
by llogiq 8y ago
I'm doing all my development on a HP Chromebook 13 G1. While the CPU is low-powered, and I since ditched the ChromeOS for a custom Linux, it's a fairly capable machine, and very cheap for what it offers. My recent 1-year review is
42.
Opportunistic Mutations for Rust(llogiq.github.io)
3 points by llogiq 9y ago|0 comments
43.
by llogiq 9y ago
One of clippy's authors and maintainers here (though I didn't choose the name); why would you name such a program "lint"? For me clippy evokes the image of a well-meaning, if at times clumsy helper that tries to nudge yo
44.
by llogiq 9y ago
Data scientist/engineer here. I write Java by day, Rust by night and in both I embrace a data-driven design, where I first carefully lay out the data so that it's easy to use within the code. In hot loops, I avoid dynamic dispatch
45.
Blog: Rust Performance Pitfalls(llogiq.github.io)
3 points by llogiq 9y ago|0 comments
46.
by llogiq 10y ago
No, that's cache invalidation. And naming things.
47.
by llogiq 10y ago
As I monologued elsewhere: If C is like playing with knives and C++ is juggling chainsaws, Rust is like parkour suspended from strings&wearing protective gear. It'll look ridiculous at times, but you'll be able to do all sorts
48.
by llogiq 10y ago
Last time I checked, the race detector could only find a certain percentage of data races – those easier to detect . The crux with such systems is you tend to rely on them...
49.
by llogiq 10y ago
The problem is that safety doesn't sell. If you're getting a new IoT heat lamp you look at the price and not the firmware's code. To your surprise, the first hacker coming along toasts your cat.
50.
by llogiq 10y ago
I'm a polyglot programmer and for me Rust is mostly about the awesome abstractions and the great community.
51.
by llogiq 10y ago
I'd really love to be there. My third child will probably be about 3 or 4 weeks old by that time, so I at least have good reason to miss out.
52.
Shave Some Time from Your Travis Builds(llogiq.github.io)
1 points by llogiq 10y ago|0 comments
53.
[Rust] Announcing Overflower(llogiq.github.io)
2 points by llogiq 10y ago|0 comments
54.
by llogiq 10y ago
This percentage includes people using explicitly unstable things (e.g. me).
55.
Writing a Rustc plugin to instrument code(llogiq.github.io)
1 points by llogiq 10y ago|0 comments
56.
by llogiq 10y ago
Doctests were employed in languages far older than Rust, e.g. python and Lua (full disclosure: I wrote doctest.lua), and there are doclets for Javadoc that give it the same functionality.
57.
Blog: cargo install clippy(llogiq.github.io)
8 points by llogiq 10y ago|0 comments
58.
Blog: Mapping Over Rust Arrays(llogiq.github.io)
1 points by llogiq 10y ago|0 comments
59.
by llogiq 10y ago
I just call it a lint because it uses the rustic::lint API. And I posited that such analysis belongs in the compiler. However, lints no longer need to be lightweight; I've seen full-program analysis passes called lints. And in rust, li
60.
by llogiq 10y ago
By the way, I recently tried to get rid of some `vec!`s in the benchmarksgame entries (well, to see if I could), but got into trouble with IntoIterator implementations, so an extension of EscapeAnalysis would be great!

More ›