yoshuaw

10 ms·

61.
by yoshuaw 3y ago
> […] just for having a different point of view was the right thing to do by the Zig leadership team From reading these threads it’s less about the opinions you hold and more about how you behaved, no? Zig leadership asked you to not pla
62.
by yoshuaw 4y ago
Yay, I’m glad that made sense!
63.
by yoshuaw 4y ago
Not all effects, but a select set which are covered by the `effect` keyword. That set could change over edition bounds. The reason for that is because we don't just care about maximum expressivity, we also care about ensuring good re
64.
by yoshuaw 4y ago
What you’re highlighting here is something we explicitly call out in the blog post as what we don’t want people to have to write. We agree the syntax is noisy and would be bad to work with. We instead would prefer it if people could write
65.
by yoshuaw 4y ago
When I wrote that I didn’t really understand the difference in terminology between “effects”/“effect types” (e.g. keyword-based modifiers on functions and types) and “effect handlers” (e.g. typed co-routines). Many effectful languages
66.
by yoshuaw 4y ago
> Right now none of the Passkey syncing providers support anything like that (and I feel like they won't, because it'd be a huge vector for scams). Within the Apple ecosystem Passkeys can be shared with contacts through AirDrop
67.
by yoshuaw 4y ago
Rust Async WG member here: This question comes up pretty regularly when people first learn about async Rust. I suspect it’s because performance is often emphasized as the main benefit of async Rust. In my opinion performance is always relat
68.
by yoshuaw 4y ago
> Why would CloudFlare do anything like that??? Do anything like what? Address controversy? It’s common for companies to issue public statements when they’re in hot water. Or did you mean doing something about bad actors? It certainly is
69.
by yoshuaw 5y ago
> One mechanism that doesn't seem to be mentioned is the .net style "manual" cancellation where CancellationToken is passed around everywhere and manually checked, often throwing an exception to early return. The async-rs&
70.
by yoshuaw 6y ago
Yes, exactly. Rust already allows for switching global allocators through `#[global_allocator]`. But now also allows plugging allocators inline through the allocator-api methods. I'd imagine something similar could be introduced for th
71.
by yoshuaw 6y ago
MSVC's C++ Parallel algorithms library gets close [1], and so does Rust's Rayon crate [2]. C# has parallel for loops [3], and apparently so does PowerShell [4] Though none of these are quite as convenient as I think they could be.
72.
by yoshuaw 6y ago
Heh fun: this was inspired by Rustlings, which in turn was inspired by NodeSchool. Mozilla Berlin used to host NodeSchool and the Rust Hack & Learn evenings. It became a bit of a hang spot, and at some point we had a pretty consistent g
73.
by yoshuaw 6y ago
That's really cool, I had no idea! Did a quick search on this, and I believe the Linux portion of this is the responsibility of the "UNIX-Class Platform Specification Task Group" [1]. They seem to be quite active, which I&#x2
74.
by yoshuaw 6y ago
Thanks for sharing this! I was wondering how much work it'd be to build a graphical Windows app using Rust, and glad to learn it's actually not too bad!
75.
by yoshuaw 6y ago
Why do you presume that group is aging and not regularly rotating people? A dozen people sounds like a standard team size to me, which seems mostly indicative of the scope (not importance) of the work. Also I believe Microsoft employs somew
76.
by yoshuaw 6y ago
Didn't GitHub spin off from Tekkub's hub back in the Burning Crusade days? Fun to see GitHub still being used to enable writing WoW addons a decade later.
77.
by yoshuaw 6y ago
I read "safely call" as "does not require `unsafe {}` to call". Invariants will still need to be manually upheld to ensure the C++ code will work as expected.
78.
by yoshuaw 6y ago
Sure do. Substack the company was founded in 2017 [1]. At that point Substack the person was already a household name in open source — with 76.000 GitHub stars to his name his projects' popularity were on par with the likes of Mozilla
79.
by yoshuaw 6y ago
> Prior to taking on a16z riches, Substack was a cool indie brand. The name "Substack" was co-opted from James "Substack" Halliday [1][2], a well-known hacker in the Node.js community. It wasn't an indie-brand-tu
80.
by yoshuaw 6y ago
One example is authoring USDT probes. This is done by writing inline assembly comments [1] that the kernel can then trace when instructed to. Also people doing cryptography things occasionally need access to specific ASM instructions for th
81.
by yoshuaw 6y ago
Oh cool, they've also authored a Tide integration: https://docs.rs/async-graphql-tide . As someone who works on Tide, this is really exciting! At a glance the integration between the two looks fairly straightforward --
82.
by yoshuaw 7y ago
It relies on async-std's behavior, which will propagate the panic.
83.
by yoshuaw 7y ago
This library assumes `async-std`; the way it parallelizes work is by spawning tasks on an executor, so by design it needs to have access to one. Without that we couldn't provide the API we do. I haven't tested it with `hyper`, but
84.
by yoshuaw 7y ago
Hi, author here. Glad you've enjoyed the post! To answer your questions: As leshow pointed out, Rust uses the Result type to propagate errors. The way we'll integrate this in parallel-stream is by adding `try_for_each`, `try_fold`
85.
by yoshuaw 7y ago
Thanks for the kind words; I just got a ping on Twitter and found my way here, almost certainly because of your comment. Thank you (:
86.
by yoshuaw 7y ago
async-std comes with its own work-stealing executor built on the async-task and crossbeam-deque crates by the same author. - https://docs.rs/async-task - https://docs.rs/crossbeam-deque
87.
Modeling Async Concurrency in Rust(blog.yoshuawuyts.com)
5 points by yoshuaw 7y ago|0 comments
88.
by yoshuaw 7y ago
Last I heard there's a fair chance that this might be implemented at the MIR level instead, allowing it to be unblocked from the LLVM bug.
89.
Rust Streams(blog.yoshuawuyts.com)
2 points by yoshuaw 7y ago|0 comments
90.
by yoshuaw 7y ago
Datrs dev here. I implemented all of the Hypercore feed protocol last year. The next step was to add the networking layer, which was blocked on async IO in Rust. So that's what I've been working on this year (the Runtime project).

More ›