@zeddotdev I‘m confused, multi-root/repo projects on both local and remote hosts were already supported before - and it is still not possible to work across a mix of local and remote folders. what is actually new with regards to „multiple repos“?
This is very cool work. Since I’m not super familiar with the domain, is there any published work around code understanding/querying? Is context size a limiting factor here for non trivial code bases?
New Project Zero blog post by Sergei Glazunov and Mark Brand: Project Naptime: Evaluating Offensive Security Capabilities of Large Language Models https://t.co/txvkXH5oCC
Software transactional memory is probably the one thing I miss the most from my Haskell developer times. IMO it is the most intuitive way to write concurrent code by far. It‘s wild to see it implemented in such a complex context as C++, amazing effort
Are there any details known about what makes a WiFi “unsafe to join” according to iOS Lockdown Mode and thus causes disconnects on each sleep/wake cycle of the phone? Seems like WPA support and TKIM are two such properties, but there are likely more.
@jduck@5aelo@farazsth98@adhsec@silviocesare@mboehme_ There was/is no actual issue/bug in the code (the switch is exhaustive), what is being considered here are just ideas to nudge the compiler to reliably produce a compilation output that has the intended security properties (which are a superset of those provided by C++ itself)
@5aelo@jduck@farazsth98@adhsec@silviocesare@mboehme_ I see, so I assume the “sound” combination is where you tell the compiler that the value can be out of range (via `: int`), AND you make the switch exhaustive even in that case via an UNREACHABLE default case …