Ville Voutilainen

890 posts

Ville Voutilainen

Ville Voutilainen

@CplusplusVille

The bane of all irrational C++ proposal authors

เข้าร่วม Kasım 2021
29 กำลังติดตาม304 ผู้ติดตาม
Ville Voutilainen
Ville Voutilainen@CplusplusVille·
In C++, class VolumeObserver : android::os::CallbackInterface // same as 'implements android.os.Handler.Callback' class ContentObserver : public android::database::ContentObserverInterface // same as 'extends android.database.ContentObserver I can Kiss The Sky.
English
0
0
1
63
Ville Voutilainen
Ville Voutilainen@CplusplusVille·
@jfbastien Language! Such phrasing is hardly appropriate for pretty much any forum!
English
0
0
0
35
JF Bastien
JF Bastien@jfbastien·
I had a dream: AInux • Packages are prompts • Install = generate + test + sandbox locally • Output = unique binary tuned to you No apt. Just prompts. Shipping tarballs? Shipping intent!
English
5
1
17
2.3K
Ville Voutilainen
Ville Voutilainen@CplusplusVille·
@ChShersh A very nice thing about C++ Ranges is that I don't have to be a fully-qualified FP person to use them.
English
0
0
0
28
Dmitrii Kovanikov
Dmitrii Kovanikov@ChShersh·
Just learned about in C++ I'm impressed by what mainstream FP has achieved. It's also interesting to compare C++ and OCaml here because C++ managed to do some things better. 1. In C++, views are lazy out of the box. In OCaml, you need to wrap lists into Seq first. 2. In C++, you can pass pointer to member directly to filter or map by fields. In OCaml, a lambda is required. 3. In C++, you still get all the benefits of super fast code. 4. Pipe operator is EXACTLY like in Bash, so there's some cross-language consistency. OCaml still looks slightly more elegant in some places. Type inference requires less boilerplate, composable 'iter' API with 'filter' and 'map' instead of a separate for-loop, no imports, and automatic function currying. But I'm surprised that C++ turned out to be not so much bigger than idiomatic OCaml. The problem is that it's becoming harder to justify using FP languages, especially when you already have a huge legacy codebase in C++
Dmitrii Kovanikov tweet mediaDmitrii Kovanikov tweet media
English
41
20
451
44.1K
Ville Voutilainen
Ville Voutilainen@CplusplusVille·
I am in possession of a selfie with @pdimov2. His existence has been anecdotally confirmed by eye witness testimony. 😀 What, however, has not been established is evidence countering the claims that he is an artificial intelligence singularity, i.e. an AI smarter than humans. 🤣
English
0
0
2
145
Ville Voutilainen
Ville Voutilainen@CplusplusVille·
@BarryRevzin The section title at #get_bases_classes_t-and-get_data_members_t" target="_blank" rel="nofollow noopener">brevzin.github.io/c++/2025/06/09… seems like a typo, should be get_base_classes_t instead of get_bases_classes_t?
English
1
0
0
106
Barry Revzin
Barry Revzin@BarryRevzin·
It occurred to me recently that I could actually implement the Reflection TS on top of the C++26 reflection design (p2996). So I thought it would make an interesting #cpp blog post to compare the type-based to value-based models for reflection: brevzin.github.io/c++/2025/06/09…
English
1
6
27
2K
Ville Voutilainen
Ville Voutilainen@CplusplusVille·
..or rather Qt 6.12, because Other Things To Do Before That..
English
0
0
0
91
Ville Voutilainen
Ville Voutilainen@CplusplusVille·
QtStdExec now supports cancellation. Which means that closing the funny test applications now stop the running async work, instead of just cleanly waiting for its completion. Woo hoo! It's feature complete, and needs only tests/examples/docs for inclusion into Qt (6.10 or 6.11).
English
1
1
6
283
JF Bastien
JF Bastien@jfbastien·
`make` and `cmake` have `ache` in common. Coincidence?
English
7
7
81
6.7K
Ville Voutilainen
Ville Voutilainen@CplusplusVille·
Run any Sender (and by extension, any wait of any QObject signal) as a stackful coroutine: #L223-238" target="_blank" rel="nofollow noopener">git.qt.io/vivoutil/libun…
English
0
0
1
107
Ville Voutilainen
Ville Voutilainen@CplusplusVille·
@jfbastien Dude, we had .pro files earlier, and have since nuked them in favor of CMakeLists.txt files.
English
1
0
2
81
JF Bastien
JF Bastien@jfbastien·
C++’s legacy is C. A hard aspect is its file-based build model. It tried to change with modules, but arguably isn’t there. Now, C++ is considering fixes to issues including security and will introduce an enterprise ready solution: - pro files - semipro files - free tier files
English
7
1
48
3.2K
Ville Voutilainen
Ville Voutilainen@CplusplusVille·
@LauraLoomer @elonmusk You do know that your speech on twitter isn't protected from twitter itself, right? All of the free speech protections protect you from the government, not from individual enterprises, so you have no particular protected right to say anything on twitter.
English
0
0
0
4
Laura Loomer
Laura Loomer@LauraLoomer·
.@elonmusk why are you labeling 75% of the replies on my account as “probable spam”? This is an abuse of power & everyone in MAGA needs to call this behavior out. This is not what we voted for. This is totalitarian censorship and retaliatory behavior over protected free speech.
California Girl@HAPPYMANUFACTUR

@CcpSkipTracer @LauraLoomer Wow it’s not just you… it’s more the 50% of the people commenting on Laura post .. I recorded it for Laura if she needs proof later..see the 1st picture I circle ‘spam’ I had to click on it ..then scrolled & scrolled

English
302
488
2.1K
222.2K
JF Bastien
JF Bastien@jfbastien·
@PatriceRoy1 @CplusplusVille There’s significant room for improvement of implementations without breaking ABI and without adding new language features. But nobody has bothered to do the work. Lots of talk though.
English
1
0
1
70