Viewing profile — questioner8216
questioner8216
HN member- Joined
- Tue, Nov 25, 2025, 2:15 AM UTC
- HN karma
- 4
- Public activity
- 17 items
- HN profile
- View on Hacker News ↗
About questioner8216
No profile information was provided.
Recent public activity
-
comment
Comment #46071233
[flagged]
-
comment
Comment #46064479
I am not breaking any rules, instead my comments are on point and show better debate culture than other comments, including better than yours and the previous comment. Please do be…
-
comment
Comment #46056926
[flagged]
-
comment
Comment #46056168
It seems completely clear. He first gives unidiomatic C++ code, then next gives idiomatic Rust code, and differentiates the two based on the code snippets. It is a mistake on his p…
-
comment
Comment #46053297
I have not given it much thought, but it would primarily be for the subset of Rust programs that do not need zero-cost abstractions as much, right? Since, even in the case of no pa…
-
comment
Comment #46053248
When comparing languages, posting unidiomatic code, and then making claims based on that unidiomatic code, is generally not fair nor correct.
-
comment
Comment #46048160
I am not sure that I understand what scoped panic hooks would or might look like. Are they maybe similar to something like try-catch-finally in Java? Would the language force the p…
-
comment
Comment #46046959
Right, I forgot that 'const' in Rust is 'constexpr'/'consteval' in C++, while absence of 'mut' is probably closer to C++ 'const', my apologies. C++ 'constexpr' and Rust 'const' is …
-
comment
Comment #46044505
But Rust's async is one of the primary ways to handle concurrency in Rust, right? Like, async is a core part of how Tokio handles concurrency.
-
comment
Comment #46044086
Good points. I have also heard others say the same in the past regarding Go. I know very little about Go or its language development, however. I wonder if Go could easily add some …
-
comment
Comment #46043130
That is a different topic from what I wrote about. The article wrote: > Automatic unlock: When you lock, you receive a guard. When the guard goes out of scope, it automatically unl…
-
comment
Comment #46043088
For that last example, if 'item' is immutable, there is no issue, correct?
-
comment
Comment #46043075
Rust concurrency also has issues, there are many complaints about async [0], and some Rust developers point to Go as having green threads. The original author of Rust originally wa…
-
comment
Comment #46043015
I dislike some of this article, my impression is similar to some of the complaints of others here. However, are Go programs not supposed to typically avoid sharing mutable data acr…
-
comment
Comment #46042364
That sounds really interesting, whether it is done in Rust, some Rust 2.0, or a successor or experimental language. I do not know whether it is possible, though. If one does not un…
-
comment
Comment #46041823
I am not very familiar with C++'s API, but I believe that you are right that the C++ example in the article is incorrect, though for a different reason, namely that RAII is support…
-
comment
Comment #46041706
Questions for anyone who is an expert on poisoning in Rust: Is it safe to ignore poisoned mutexes if and only if the relevant pieces of code are unwind-safe, similar to exception s…