Is Canada Europe too?
- Former C++North now NDC Toronto (announced today bsky.app/profile/greg...) Heard only good things about it, want to attend.

@cpponsea.bsky.social ... CppOnSea / AccuOnSea, Folkestone, UK
CppUnderSea ... Netherlands (I wasn't I was supposed to go, but due health issues I couldn't go)
`using std::c++` in Madrid ... a free to attend conference at the university there
2/n

Conferences I like (and I hope I won't forget about any)
@meetingcpp.bsky.social ... the european C++ conference (in Berlin)
@codedive.bsky.social ... one day but really large conference (2024 it was ~1500 people) in Wrocław
@ndcconferences.com (NDC TechTown) ... in Kongsberg, Norway
1/n

Some people don't train them well. They are very intelligent and stubborn. Sometimes almost cat like.

Definitely not true. They can be stubborn or too sensitive "but it's too cold and wet, what about not going at all?". But with some consistence it's manageable. Charlotte didn't do any crime for over seven years now. Actually she is the one giving me some daily routine.

alternative would be to introduce a magic function to query if allocation is non-transient region, and skip delete on it (or just make delete ignore these)

I think at start we can allow only immutable output where you must prove non-const pointer can't leak the object, and if we want mutability, we can make calling `delete` on such memory a UB, I know it's scary, but because static objects are destroy in infinity, it won't really matter

that's the point, then you can integrate libclang in chromium, and have <script type="application/constexpr-c++">crimes</script>

updated version of that slide

we still don't have non-transient allocation ... so any allocation you do in compile time, you must release it during the enclosing constant evaluation, but from there you can `std::define_static_array/object/string` and get array representing `[.begin(), .end())` range representing the container

yes, I forgot ... ALL [containers] ... constexpr map, constexpr set, constexpr unordered_map, constexpr list, constexpr deque, constexpr hive (this one still somehow pending), constexpr stack/queue ... you name it :) ... and of course constexpr flat_map/flat_set and constexpr inplace_vector

for C++29 we will have constexpr coroutines & generators (both in wording groups), constexpr pointer tagging (via a special magic type), constexpr (shared_)mutex / locks / conditional_variable

we also have constexpr exception throwing (and catching and rethrowing) in c++26 😘

and constexpr virtual inheritance (which takes us closer to constexpr basic_iostreams (mostly string_stream and span_stream)

that what it means :) atomic<T> and atomic_ref<T> (not volatile T) are both usable in C++26...

also atomic<shared_ptr<T>> ... and shared_ptr<T> 😅

Yes!!