Viewing profile — yuushi
yuushi
HN member- Joined
- Wed, Jul 22, 2009, 6:50 AM UTC
- HN karma
- 101
- Public activity
- 44 items
- HN profile
- View on Hacker News ↗
About yuushi
No profile information was provided.
Recent public activity
-
comment
Comment #28400325
Except this (attempted) mask mandate ban was for kids - i.e. those who are often too young to receive a vaccine. Yes, our federal government absolutely failed when it comes to vacc…
-
comment
Comment #28400087
It is not endemic in many states in Australia. But please, continue looking on in horror at us from (I'm assuming) America. Your post is a wonderful mix of condescending tone and f…
-
comment
Comment #26734657
That's because modules and namespaces are the same thing in languages like Python, whereas they are separated in C++. The code in the imported module will go into whatever namespac…
-
comment
Comment #26734162
Modules have nothing to do with shipping libraries (or dependency management), they are purely about encapsulation of interface and (API) implementation.
-
comment
Comment #25759482
If by "reload" you mean "drop in an updated shared library and let the runtime loader do its job", I suppose so. Yes, it only applies if you don't make any API (and ABI) changes, b…
-
comment
Comment #21750303
> I can't remember the case in C, but in C++ the initialisation of a function local static variable is guaranteed to be thread-safe. Only in C++11 onwards.
-
comment
Comment #21750264
Depending on what you required, it can still be significantly faster than std::map. Any tree-based data structure is going to play havoc with cache. Also, it will perform an alloca…
-
comment
Comment #21750202
Define "way easier". The interface, at least for day to day operations, is basically identical.
-
comment
Comment #21308754
I remember this being in the context of video games, and from some time ago (so things may have changed with Steam sales and the like), but it said that something like 85% of sales…
-
comment
Comment #21154623
Correctness defined as "this produces the right answer" vs correctness defined as the above with the addition of "this does not leak information / is not highly vulnerable to side-…
-
comment
Comment #18870744
I mean, you really are a special case - I have only lightly dabbled in Rust, but I immediately recognize your name because of the work you've done in the Rust community.
-
comment
Comment #18870719
If you have the luxury of choosing between C++ and Java/C#, then you don't need C++.
-
comment
Comment #18853928
This doesn't take into account the alignment of the type though (you'd want to use std::aligned_storage ), but that requires knowing enough about T to be able to use sizeof() and a…
-
comment
Comment #18012635
This could only ever be doable with extremely simple architectures anyway. Off the top of my head, add in just one of branch prediction, micro-op fusion, out-of-order execution, pi…
-
comment
Comment #16554497
Sure, you can pass by pointer instead of reference, but the post also mentioned that they didn't use the STL (hence no std::vector) and I'm curious if that means they used a replac…
-
comment
Comment #16550365
> SIMD Intrinsics are directly callable from C++. > likely/unlikely branches Most compilers have extensions that will allow you to do this (__builtin_expect and so on). > in-lining…
-
comment
Comment #16550306
The second is absolutely an advantage of references, and other than having to use (if I'm being honest, legacy and/or bad) interfaces, there is absolutely not a downside in this re…
-
comment
Comment #16550294
Out of curiosity, what do you use? I hope it isn't back to raw pointers and size_t offsets for lengths. What do you do if you want to pass a container of ... anything around? What'…
-
comment
Comment #7209568
Go is not even close to being any kind of replacement for C++. Also, not all "real programmers" think that C is a better language than C++.
-
comment
Comment #6984845
They were bought out by iiNet. Apparently Adam also signed deals for a takeover by iiNet in August this year.
-
comment
Comment #6744080
It shouldn't be the standard way of managing memory; it should be a part of the toolkit. In order, it should look like: 1) Stack allocation 2) std::unique_ptr 3) std::shared_ptr Yo…
-
comment
Comment #6715342
Sure. Think of void * in C. interface{} in Go isn't really that different, there's just a bit more language support for testing if it satisfies a specific type or not. Add in type …
-
comment
Comment #6709819
I think interface{} is a horrible, horrible hack. For me, the answer is an emphatic yes.
-
comment
Comment #5696648
I remember having read this before, but I always get a good chuckle from it; all of the snark is incredibly well done. I always burst out laughing when reading "Lambdas are relegat…
-
comment
Comment #5497145
Why does it have to be limited to a single language at all? Exposure to multiple languages should be the norm.