Jared

i want to go on a DATE. that means you CALL me and make plans IN ADVANCE. then you PICK ME UP and take me to the ANIME CONVENTION

McDonaldlanders SHOCKED When I Order in McDonaldlandese

i just hope all the candidates have fun

imagine having to give kamala your alpha black lotus

dude gets another year older after trying really hard not to

what would be on pure moods 2024

the world according to ZIRP

insane that jesus had 12 friends at 33

@seanbax how does the compiler know that the borrow returned from split_left is related to the input parameter?

Cool cool I have a rudimentary slice primitive that is compatible with the borrow checker. The borrow checker threads lifetime information (a set of points in the CFG) from the entity that owns data through to all of its consumers, even through function calls.

@seanbax eXtended Circle Object Model could also work :0)

@chaffg New Circle Object Model. Basically Rust's object model, but C++.

This is very nice. I'm lowering C++ to a MIR, and this new code is far more organized than my LLVM codegen. The aim is for drop elaboration to kick in after this and use live analysis to kill unwanted drops. A useful amount of AST lowers and it only took a week to get here.

practicing self-love for lent

the only reason they shot it down is so they can put it on ebay

the epoch times is reporting that the CCP has peed in all of our cokes

jim and pam were never prosecuted for their crimes

my high school senior portraits as an 80s dark fantasy film

the dad in a christmas story was 32 years old

in 2023 i will skim a wikipedia article each hour

@seanbax you should make every english preposition an overloadable operator

Ok first cut on the [as] and [no_implicit_narrowing_conversions] features. The latter turns off narrowing conversions. The former lets you enable them with 'x as _'. It's also a more beautiful static_cast: 'x as y' is equivalent to 'static_cast<y>(x)'. Big ergonomic win.

@seanbax the last one

How should you indicate a pack parameter using the name-on-the-left declaration style? func(x : int); template<typename... Ts> func(x... : Ts) ? func(...x : Ts)? func(x : ...Ts)? func(x : Ts...)?