Viewing profile — mbel
mbel
HN member- Joined
- Wed, Oct 26, 2011, 11:57 AM UTC
- HN karma
- 1,309
- Public activity
- 348 items
- HN profile
- View on Hacker News ↗
About mbel
Recent public activity
-
comment
Comment #48204881
Unless your code targets some exotic architecture, like idk x86.
-
comment
Comment #47333683
Yeah, totally, just one more year.
-
comment
Comment #46564256
Nobody would say „trujący wąż” (poisonous snake) or „jadowity grzyb” (venomous mushroom). The distinction is similar to English. There are exceptions and contexts where it can be u…
-
comment
Comment #46561955
Not really, we have both „jad” (venom) and „trucizna” (poison).
-
comment
Comment #46470802
The primary use case that I can see is following: you use your second phone — the communicator — to chat, while watching endless stream of tiktoks/reels/shorts on the first one.
-
comment
Comment #46319984
> In terms of CPU? The other way around. That depends on your architecture and access pattern. In case of sequential access, packed bools may perform better due to arithmetic being…
-
comment
Comment #46047020
> It’s less simple than many systems languages because it has a very strong type system. I don’t think that’s the case, somehow most ML derived languages ended up with stronger typ…
-
comment
Comment #45465372
In this case there is both time a distance limit to the gesture. If the gesture is too fast the switcher won’t appear even if the distance was long enough. That said, personally I’…
-
comment
Comment #45325588
It feels like a stretch to call this a parser. It’s looks like a typical lexer?
-
comment
Comment #44149309
Probably the compilation time is better than it would be with LLVM. On the other hand I doubt that codegen and therefore performance is on par with LLVM. Definitely a weird thing t…
-
comment
Comment #43812385
This is mostly an issue with MSVC which refuses to become compliant with c99 standard. Their support for c11 and c17 also has some gaps around features that were introduced in c99.…
-
comment
Comment #43775029
Most popular languages would prevent this. In this case it’s as simple as having more sensible reader API than sscanf in standard library and forcing variables to be initialized.
-
comment
Comment #43663351
To be honest the implementation looks surprisingly readable… at least compared to other horrors like the standard library implementation. While there are some new rules regarding a…
-
comment
Comment #43320422
It's explained under the first link from the article [0]: "A new type of interpreter has been added to CPython. It uses tail calls between small C functions that implement individu…
-
comment
Comment #42993967
Yup, they most likely do. After all everything is LLVM based nowadays.
-
comment
Comment #42803408
It seems to work similarly as in C, i.e. you call malloc manually, there is some form of automatic size deduction though: https://github.com/galileolajara/cp1/blob/main/examples/04…
-
comment
Comment #41464326
For Intel you can just look into sources: https://github.com/intel/intel-graphics-compiler ;) Also AMDGPU and NVPTX targets in LLVM might be interesting.
-
comment
Comment #39464465
Standard word which implies some level of analysis into causes of the incident. This brief note doesn’t live up to industry practice either.
-
comment
Comment #39289295
It's not. 0x8000 is the smallest (-32,768) integer that can be represented with 16-bits and two's complement.
-
comment
Comment #34968855
I see, thanks for clarification! I glanced though their website and expected a standard set of features including IMAP.
-
comment
Comment #34968744
It’s an email service, the app isn’t really needed.
-
comment
Comment #33025656
Here's an attempt at doing that: https://dreamfusionpaper.github.io/
-
comment
Comment #32010939
Using intrinsics is much more sensible option than dropping to inline asm. Each CPU with SIMD or any kind of specialised instructions provides an intrinsics library for C.
-
comment
Comment #31185571
Interesting that CSV is supported but XML is missing. Is it finally dead?
- comment