foonathan

7 ms·

1.
by foonathan 2y ago
Saying "XXX is an asshole" if XXX is in fact an asshole is also the objective truth, yet warrants removal for insulting someone.
2.
by foonathan 2y ago
It's not silenced, the post is up for all to see. We have just disabled the ability to post new comments under it.
3.
by foonathan 2y ago
> one obvious gap is that it doesn't seem to have a statement from the person removed after they were removed. I think the article is written by the person that was removed. It is lacking any statement of the standard foundation who
4.
by foonathan 2y ago
> That is not true. I banned you, so I like to think I'm an authority on why you were banned. Here's a step by step timeline of what happened. 1. This comment of yours received a high number of reports and was automatically fil
5.
by foonathan 2y ago
> I participated for r/cpp for a very large number of years, including quite a number of high-impact posts - just not with that account. Interesting that you did not choose to voice your opinions using your main accounts on that com
6.
by foonathan 2y ago
Hey, u/ss99ww. We did not go on a banning spree, we banned only one person, you. After removing the comment we're you insulted someone, I checked your history, noticed that you did not meaningfully participate in r/cpp outsid
7.
by foonathan 2y ago
Here's an explanation: https://www.reddit.com/r/cpp/comments/1coi2kq/comment/l3fblu...
8.
by foonathan 2y ago
Oh, that's just a side effect of the way the work is distributed :D I'm hired to maintain our core libraries and general C++ stuff, and I write most of the blog articles, so it's about the problems I face in my everday work.
9.
by foonathan 2y ago
Yes, but sadly I have to use Boost.Spirit at work :(
10.
by foonathan 2y ago
Post author here. To be fair, we specifically don't use std::ranges because of that "N Pythagorean triple" problem. We have our own custom library that is vastly superior to std::ranges. See e.g. here for context: https:&#x2
11.
by foonathan 3y ago
You subscribe to the Github issue of the proposal: https://github.com/cplusplus/papers/issues
12.
by foonathan 3y ago
There are two reasons for that: Herb didn't attend in person and the meeting was in Golden Sands, not Varna...
13.
by foonathan 4y ago
I'm currently writing an interpreter for C, I plan on adding a JIT at some point as well: https://github.com/foonathan/clauf
14.
by foonathan 4y ago
> This is especially weird because Jonathan explicitly calls out the "new languages" like Carbon and whatever Herb will call his thing. You overestimate my knowledge of Rust :D I wasn't aware that NonZeroU32 is a thing, th
15.
by foonathan 4y ago
To be fair, std::unordered_map is also very slow in release mode.
16.
by foonathan 4y ago
Based on what they've told me the long term governance plan is to establish an independent foundation, with development controlled by three equal lead developers from different companies. It may have been started by mostly Googlers but
17.
Show HN: Lexy – C++ parser combinator library with custom DSL(lexy.foonathan.net)
1 points by foonathan 4y ago|0 comments
18.
Lexy: C++ Parsing DSL Library(lexy.foonathan.net)
2 points by foonathan 4y ago|0 comments
19.
by foonathan 9y ago
The conclusion is "yes, we still need it".
20.
by foonathan 9y ago
There are attributes like `[[gnu::always_inline]]` for GCC and clang.
21.
by foonathan 9y ago
Author here, I didn't intend to give a motivation for purging it, many people in the C++ community want to and I wanted to explore the feasibility of that in the current status. > like embedded systems or digital signal processing,
22.
by foonathan 9y ago
$ is already a valid identifier character in a clang and gcc extension. And there won't be reflexpr and $, those are two different proposal. And due to the extension, it won't be $ (most likely).
23.
by foonathan 11y ago
And I've showed one way to do the matching in an automated way. How you wrap those implementation things, is up to you. I agree, overloading might have problems.
24.
by foonathan 11y ago
Even if you named the functions differently (clz8/16/32/64), you still needed to match them to the appropriate __builtin_clz version.