nihohit.bsky.social
16 posts
11 followers
28 following
Conversation Starter
comment in response to
post
Yup.
comment in response to
post
IMO even weirder is that Arc<T> can be two different types.
comment in response to
post
Shadowing makes perfect sense when variables aren't reassignable by default. I'm not so sure that combining reassignable and mutable into a single keyword was the right choice, though.
comment in response to
post
Your best soundtrack IMO
comment in response to
post
V! For VeDequeue!
comment in response to
post
But that's an engine consideration. How many games require their logic to be so parallel, at the cost of slower iteration times?
comment in response to
post
Testing the function a+b with a=1,b=1 will satisfy line coverage, bit won't test for overflow.
comment in response to
post
> Currently there are good async implementations for TCP in the async-std, Tokio and Smol projects.
I see that you're in the same boat as me :)
comment in response to
post
I just added support for smol to redis-rs (github.com/redis-rs/red...), and it was relatively painless - or at least, as painless as a 900 line PR can be. Occasionally I consider adding monoio support, but I haven't found a way to do that without unsafe code, or writing everything from scratch.
comment in response to
post
C++ is in the process of introducing reflection. If facet can be combined with that effort to enable safer interop, I think that Google is funding efforts in that direction.
comment in response to
post
side note - the blog links to your deactivated twitter user, not here.
comment in response to
post
... solved in user space, but I haven't seen anything that tries to integrate with the underlying mechanisms, only with the user-space APIs. This means added costs, unsafety, and again and again finding that threads are accidentally blocked.
comment in response to
post
One big issue is integration with other languages' async runtime. The amount of potential and actual pitfalls that wait for truly performant cross-async code is horrible. Also, it's language specific, and whatever mechanism you develop in lang A won't work for lang B.
I'm not sure it should be ...
comment in response to
post
I compeltely agree that pestering people about their choice of language is absurd, but the blog post explaining this choice managed to be both weirdly apoplogetic, and not provide a concrete explaination for the choice. They would've been better just (rightfully) not trying to explain that.
comment in response to
post
ATM Balatro, but it has 0 story.