JF Bastien

@jfbastien.com

Build & scale platform — working on humanoid robotics 🤖 🔗 https://jfbastien.com 🔗 https://tlbh.it 📍 東京、日本

OMG i live in japan and love signage can you please tell me what grocery store this is in!!! i will go see it at some point (DMs are ok too!!) see also: a grocery store sign i went to see two years ago

Bild

For all the recent supply chain security attacks, I find it fascinating that C++’s standard package manager hasn’t been attacked. Tells you a lot that nobody is criticizing C++’s security right now!

France: 𝒜𝓅𝓅𝑒𝓁𝓁𝒶𝓉𝒾𝑜𝓃 𝒹’𝑜𝓇𝒾𝑔𝒾𝓃𝑒 𝓅𝓇𝑜𝓉𝑒́𝑔𝑒́𝑒 Japan: Just so you know… this one’s gonna STINK (it’s really good)

Bild

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!

When are they rewriting Unix `tee` in Rust? It’s only 350 lines of code. 🦀 Seems to me like the easiest way to achieve memory safe tee everywhere. 🙃

It's going to take a bit more time for the collaborative trip report to make r/cpp, so here's an explanation on what happened with C++ profiles, their relevance to safety/security, and why this is a great outcome for quality of the feature and speed of delivery.

For profiles, we voted the following:

Pursue a language safety white paper in the C++26 timeframe containing systematic treatment of core language Undefined Behavior in C++, covering Erroneous Behavior, Profiles, and Contracts. Appoint Herb and Gašper as editors.

   

What does this mean?
  Many people felt that what profiles are trying to address (security, safety) is hugely critical... yet profiles as they stand today are not ready. The C++26 train is leaving the station, but we want progress, now!
  Enter white papers: it's a tool that ISO is now encouraging us to use, whereby we need WG21 plenary approval and SC22 approval, and then we have an approved white paper. The implication: We can get profiles in a white paper, implemented in compilers (behind a flag) before C++26 is finalized.
  How does that work? White papers are a lightweight TS, or a heavy paper. The way we manage this is fairly open and we heard concerns which Herb and Gašper will suggest ways to address. For now, we have them as editors, they choose what goes in the white paper, and our hope is that they are trusted by everyone to do so while increasing consensus. EWG will see updates, forward them to CWG, then to plenary, then SC22, with votes at each stop. This is actually lightweight, and will allow rapid improvements and feedback. One way to address issues brought up is to have a git repo on github.com/cplusplus where the white paper is developed, with great commit messages, with periodic reports (say, monthly), and with periodic EWG telecons to review (say, monthly). Herb and Gašper will publish details soon.

(alt text limited, see r/cpp post when available for the rest)

Join our Tokyo C++ Meetup on “Abstractions for Low-Level Programming”, featuring @lefticus.bsky.social ! Learn how to balance performance & complexity and more. ✅ Date & Time: February 20, 2025, 6:30-8:30 pm (JST) 👋 RSVP by February 13th at 12 pm! peatix.com/event/4273915

C++ Meetup in Tokyo - Abstractions for Low-Level Programming

C++ Meetup in Tokyo - Abstractions for Low-Level Programming (日本語は英語の後に続きます) Programmers w...

peatix.com