squiguy7

8 ms·

31.
A Rusty Go at Channels(gsquire.github.io)
5 points by squiguy7 8y ago|0 comments
32.
DivANS: Modular Compression(dropbox.github.io)
4 points by squiguy7 8y ago|0 comments
33.
by squiguy7 8y ago
A few things that help keep me sane: - Exercising (doesn't have to be strenuous, can just be a walk around your neighborhood) - Writing my thoughts down when I am overwhelmed - Never trying to keep too much information in my head at on
34.
by squiguy7 8y ago
Ok, great. Thanks for sharing the information as it is! :)
35.
by squiguy7 8y ago
It's cool to see CloudFlare using Rust but I wish they went into a little more detail on the slides. I hope to see follow up blog posts or some of the code open sourced soon.
36.
by squiguy7 8y ago
For some reason listening to metal makes me focus so I will often have that on in Spotify. Some bands include Rosetta, Neurosis, and Amenra.
37.
by squiguy7 8y ago
In this example: fn foo(x: i32) -> Box<Iterator<Item = i32>> { let iter = vec![1, 2, 3] .into_iter() .map(|x| x + 1); if x % 2 == 0 { Box::new(iter.filter(|x| x % 2 == 0))
38.
by squiguy7 8y ago
One of my favorite features of this crate is the RegexSet [0] type. It can be useful to check input against a set in O(mn) time and still have the flexibility of a regex. (m is the size of the RegexSet and n is the length of the text you ar
39.
Alias-Based Formulation of the Borrow Checker(smallcultfollowing.com)
1 points by squiguy7 8y ago|0 comments
40.
A Formal Look at Pinning in Rust(ralfj.de)
4 points by squiguy7 9y ago|0 comments
41.
by squiguy7 9y ago
I understand some people's motive to fork OpenSSL but don't hear much about the success of these forks in the wild. Does anyone have any information on how BoringSSL or LibreSSL is used? It'd be great to hear from maintainers
42.
Atomics and Memory Ordering(vorner.github.io)
2 points by squiguy7 9y ago|0 comments
43.
A Tale of BFS(medium.com)
1 points by squiguy7 9y ago|0 comments
44.
by squiguy7 9y ago
I have seen https://cronitor.io/ in the past. Are there any differences from this service?
45.
by squiguy7 9y ago
> You can use old editions indefinitely on new compilers; editions are opt-in. This is great to hear! A best-effort backwards compatibility guarantee is important to have for a language that has a lot of development.
46.
by squiguy7 9y ago
I would have liked to have seen how the author measured the hot spots in the graph. It wasn't immediately obvious to me that the `WriteToUDP` function was taking up a significant portion of the call. Another thing that is omitted is wh
47.
Coping with Mutable State in Rust(medium.com)
3 points by squiguy7 9y ago|0 comments
48.
by squiguy7 9y ago
It depends on your use case. You may find `String` [0] easier to use since it is growable, etc. As you continue to use Rust you will find that each type has their reason and string slices (what are used in this blog post) have their limits.
49.
by squiguy7 9y ago
Sorry, yes. This page has some documentation on what I meant: https://doc.rust-lang.org/beta/nomicon/lifetime-elision.html
50.
by squiguy7 9y ago
> I may express here a crucial point, LIFETIMES ARE HARD TO DEAL WITH, so try to not use them to often. While this can be true, you are always dealing with them if you have a reference to something. Sometimes the compiler will elide them
51.
by squiguy7 9y ago
This article didn't dive too deep into what this service offers but every company I have been at has this problem. And each time there seems to be a different way of sharing credentials whether it's passwords, certificates, or key
52.
by squiguy7 9y ago
There is some good discussion on /r/rust [0] as well. I'm not trying to invalidate the author's post but rather share some more insight. [0]: https://www.reddit.com/r/rust/comments/7z7p5m&#
53.
by squiguy7 9y ago
As with all things in life, it's about balance. I have been more than happy to review other's code because I see it as more than just a critique. Often times it is also a learning opportunity by seeing their style or approach for
54.
by squiguy7 9y ago
Another good alternative is to use sshuttle [0] which can tunnel all traffic that you instruct it to. It's quite simple to run as well. [0]: https://github.com/sshuttle/sshuttle
55.
by squiguy7 9y ago
This most likely has to do with their respective memory models. Rust will try and allocate most things on the stack unless an item is explicitly wrapped in a Box. This isn't the only exception however. I can't speak to Java's
56.
C++ Coroutine Theory (2017)(lewissbaker.github.io)
190 points by squiguy7 9y ago|52 comments
57.
Redis Modules using Rust(gsquire.github.io)
4 points by squiguy7 9y ago|0 comments
58.
by squiguy7 9y ago
I think it depends mostly on the context. If you only want to allow a known subset of items, prefer a whitelist. If you want to avoid a subset of items, prefer a blacklist.
59.
by squiguy7 9y ago
Crystal is a relatively newer language aimed to combine Ruby's syntax with the speed of C per it's project page [1]. [1]: https://crystal-lang.org/
60.
by squiguy7 9y ago
To further my understanding this would be akin to trait objects in Rust right? Instead of having generic type constraints in the function signature you can `Box` your traits or use pointers to a trait and use dynamic dispatch. I'm sure

More ›