BatmanAoD

6 ms·

31.
by BatmanAoD 6y ago
Try `git log -p <path(s)>`, which will show the sequence of diffs for only the specified set of files.
32.
by BatmanAoD 6y ago
> I'd add a recommendation at the top of this to have a Rust compiler handy. If you haven't already, check out the Playground: https://play.rust-lang.org/ It's reasonably full-featured for a web IDE (much
33.
by BatmanAoD 6y ago
A few municipalities have decided to offer fiber internet through the city, but I don't know how common that is. These projects take several years, though.
34.
by BatmanAoD 6y ago
I understand; I used Beamer back in college. It just seems like that's not really a good fit for the original purpose of PDF files. If they wanted to support presentations, maybe they should have created a new file type based on PDF bu
35.
by BatmanAoD 6y ago
Wow, that seems like a rather questionable feature for a "portable document format".
36.
by BatmanAoD 6y ago
`.inputrc` is your friend. I have `v` (in normal mode) configured to open the line in an editor, because muscle memory sometimes makes me try to enter visual mode when editing a command.
37.
by BatmanAoD 7y ago
Did it, though? AFAIK Node still doesn't have OS threads, which are the expensive version. The "About" page still says that Node is "designed without threads": https://nodejs.org/en/about/
38.
by BatmanAoD 7y ago
An `async` function _can_ call blocking functions, of course, it just blocks the entire thread of execution which could otherwise continue making progress by polling another future.
39.
by BatmanAoD 7y ago
I'm not sure I see the connection between bounded execution and having an `await` statement. Rust's `async` functions, just like normal functions, definitely aren't total or guaranteed to terminate. They also technically don&
40.
by BatmanAoD 7y ago
I hadn't heard of "synchronous concurrency", but looking at the Céu paper (only briefly so far), I think the model looks very close to how `async`/`await` works in Rust - possibly even isomorphic. This is really exciting