Well you kind of are, because you're claiming that just because birds willingly spend time in a cage with open doors, it's different than a bird in a locked cage. That's a claim that you're making. So, the question stands, what are you basing that off of?
So I was saying that rust monolithicism is NOT based on ignorance and naivety.
Do you see what I mean by nuance? I think you just glanced at the comment, saw that there were negative words around rust, and you lossy compressed into "Rust bad".
For the qualities we care about, it may turn out to be the case we don't need to simulate matter perfectly. We may not need to concern ourselves with the fractal complexity of reality if we identify the right higher level abstractions with which to operate on. This phenomenon is known as causal emergence.
> That is, a macroscale description of a system (a map) can be more informative than a fully detailed microscale description of the system (the territory). This has been called “causal emergence.”
> A highly compressed description of the system then emerges at the macro level that captures those dynamics of the micro level that matter to the macroscale behavior — filtered, as it were, through the nested web of intermediate ε-machines. In that case, the behavior of the macro level can be predicted as fully as possible using only macroscale information — there is no need to refer to finer-scale information. It is, in other words, fully emergent. The key characteristic of this emergence, the researchers say, is this hierarchical structure of “strongly lumpable causal states.”
Who are "we", and why would I care about them here?
There are situations where approximations are good enough for simulations, sure, but that's not the subject here.
I reject the idea that chatbots have feelings or intellect because they output text that is similar to what a human might write in some hypothetical situation or other. To the extent that they can have those properties, it is to the same extent as Clark Kent can, if one were to accept such a conflatory and confused discourse.
Oh there is truth behind the phenomenon of UFOs. Public perception is changing but many still understandably view this topic as conspiracy. This won't be the case for long.
The author is right about inlining but has picked the wrong example to show this since the compiler cannot inline across await.
If this function is in the hot path the last thing you'll want to do is to needlessly call await. You'll enter a suspension point and your task can get migrated to another thread. It is in no way comparable to the dead simple inlining example given later.
This is why you should always benchmark before making guesses, and to double check you're even benchmarking the right thing. In this case they used the findings from a nonasync benchmark and applied it to async. This will lead you to a very wrong conclusion, and performance issues.
Is this stated somewhere? A simple search online yields nothing, and just testing it out on godbolt the compiler does inline at least simple async functions as mentioned in the article.
Yeah the author makes a really poor example with the async case here.
Async in rust is done via cooperative scheduling. If you call await you enter a potential suspension point. You're willingly telling the scheduler you're done running and giving another task a chance to run. Compound that with something like tokio's work stealing and now you'll possibly have your task migrated to run on a different thread.
If this is in hot path making another call to await is probably the worst thing you can do lol.
The author demonstrates later with a dead simple inlining example that the asm is equivalent. Wonder why he didn't try that with await ;)
reply