Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

ADSP: Algorithms + Data Structures = Programs

ADSP: Algorithms + Data Structures = Programs artwork

Episode 234: C++Now 2025 Recap!

May 16, 202534 minAudio

In this episode, Conor and Ben chat about Ben's recent talk and attendance at C++Now 2025! Link to Episode 234 on Website Discuss this episode, leave a comment, or ask a question (on GitHub) Socials ADSP: The Podcast: Twitter Conor Hoekstra: Twitter | BlueSky | Mastodon Ben Deane: Twitter | BlueSky Show Notes Date Generated: 2025-05-13 Date Released: 2025-05-16 C++Now 2025 C++Now 2025 Schedule ADSP Episode 148: 🇸🇮 SRT23 - Robert Leahy on C++ in FinTech C++Now 2025 - Roby Leahy Talk C++Now 2025 - Sean Parent Keynote C++Now 2025 - Lisa Lippincott Keynote C++Now 2025 - Ben Deane Talk C++Now 2025 - Richard Powell Talk Python sort Python sorted C++Now 2025 - Braden Ganetsky Talk C++Now 2025 - Dietmar Kühl Talk C++Now 2025 - Andy Shoffer Talk Intro Song Info Miss You by Sarah Jansen https://soundcloud.com/sarahjansenmusic Creative Commons - Attribution 3.0 Unported - CC BY 3.0 Free Download / Stream: http://bit.ly/l-miss-you Music promoted by Audio Library https://youtu.be/iYYxnasvfx8

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show. Tap a time to play from there.

BenYou know, so so in a sense, you know, C ⁇ and Java and Python and C sharp, they're all really the same language-ish. They're all descended from Algol, right? But then something like Lisp or Smalltalk or Prologue, they are different, they are qualitatively different. They're different families.

ConorToday with my co-host Ben, we recap C now 2025. How's it going? We're we're back. All right. Yeah. It's going what pretty well. Yeah, what is it? It's May, May 13th, or halfway through May, which is I don't know what puts that percentage through the summer. Is it officially summertime now? I actually don't know. Might be spring still.

BenIt's probably still spring. You know, people say the first day of spring is the spring equinox. To me that's not really the first day of spring, but.

ConorI see. I mean it depends on where you are in the world, I guess. We don't have much spring in Toronto. It's just cold. Then there's a couple weeks and then then it's summer. Um and then sometimes it's winter for a day or two, like as a practical joke that the weather gods play on us.

BenFake spring. I would I would think you pay extra attention to spring considering how short it might be.

ConorI guess. I guess. Um I'm just happy that it's it's like uh it's 20 plus degrees-ish in in Celsius, which is it's getting it feels like it's uh summertime, at least this weekend it was it was very, very nice.

BenYeah. Same in Denver. It's but in fact it's been hotter than that even, it's been mid-20s. I think today it's uh yeah, right now it's 25 Celsius.

ConorSo into the low eighties, it's been what is it in uh it's only 13 degrees right now, but that's because I think it's about the weather people are saying it's about to rain. Or they actually say it's raining right now, which I can tell you is false, but hey, it's hard to get the weather right. Even in the moment, I guess. Um anyways, you were uh recently at uh one of the I guess not biggest.

BenWell decidedly not biggest, but but for my money, probably the best, the most enjoyable. Um C conference.

ConorThat's C now, of course, in Aspen. In Aspen, yes, up in the mountains, where the air is thinner.

BenYeah, Aspen's what, just over 8,000 feet, I think. How was how was that? Yeah. I I wasn't there, but you were, you were speaking. It was really good, you know, as it always is. You know, the this year the attendance was down a bit, you know, d distinct lack of the usual uh a lot of the usual Europeans did not attend, and also some Canadians, Tony was not there, notable by his absence. But having said that, there were lots of good talks, there were lots there were still also lots of good folks who did make it.

BenUm and it was and it was fun. There were some Canadians, Braden was there, and so was Rob Leahy.

ConorTechnically, I mean Rob's Canadian, but he's like uh how would you describe- I mean, we had Rob on the podcast, uh, one of my favorite interviews ever. We were walking through Venice post you know, wine and um, you know, much seafood, and he was one of the most articulate while walking post uh wine interviews. I mean, I guess we've only really done it with him, but I couldn't I couldn't believe how composed he stayed. And uh, but he lives if um unless if I he's moved since I last spoke to him, he lives in New York.

ConorSo he's a I'd almost consider him half Canadian, half New Yorker at this point.

BenUh well he gave a talk anyway about uh let me find the exact title. Um Extending Stood Execution was his title. So he talked about implementing custom algorithms with senders and receivers. And as is typical for his talks, he he always gives a very polished talk. I think he's taken classes in public speaking in the past.

ConorYeah.

BenAnd uh his talks are very polished, and and especially this one, because he showed a lot of C code, it was very dense. So it's the kind of talk I'm gonna want to go back and watch again on YouTube. Um but it was it was a great talk to sit in, and I I managed to follow most of it at the time, but as you know with these things, you know, when you need to go back and sort of reinforce.

ConorYeah. No, definitely. And I guess we should uh we should mention this now for the listeners that are gonna definitely be curious about this. Do we know because it's changed from years past how these videos get released. It used to be they kind of came out super quickly. I saw on Reddit now that there's like a if you're very eager, I think you can pay some money to get access ahead of time, and then they're gonna slow I don't actually know the full details. Do you know?

BenWell, so I don't know I don't really know what timeline they'll be coming out on. Um but but yes. Uh if you if you went to the conference, you do get the early access. Um or you can buy the early access as as several conferences are doing now. I I think I s I read somewhere that the first videos will be out about a month after the conference, so that will put it at the end of May. They're at the beginning of June.

BenUm and I expect, although I'm not sure the keynotes might be out before then, or certainly the keynotes are usually among the first to be released, right?

ConorYeah. Okay. Well, so as as I always do, I will link the talks in the show notes of either the website or the podcast app, but they will usually be unlinked for the first several several months. Oh, that's right.

BenThey're unlisted on YouTube, yeah.

ConorYeah. Well, not unlisted, like but it'll just be the text of the link that will be there in the future. That's just what you mean. And so I will anytime like I I peruse the C subreddit and they have those videos that have been released. Uh so whenever I notice that there's a talk that comes out, I will retroactively go back and it's better to check the website. I don't usually go back to the podcast episodes because that's more work than it's worth. But anyways, you can check back on the the website show notes for when these talks do come out.

ConorRight. Um but they will be. So if we're talking about a talk, you might not be able to watch it today. But if you're listening to this, you know, months in the future, so not May of 2025, it's probably already out online. So you can go check out Rob's talk and any of the other talks we're about to talk about, including yours.

BenYeah, yeah. So there were three keynotes. Um Sean gave the first. I saw that. How was that? You know, it was good. It w it was really good. Um, Sean will forgive me for saying this, but and I'm in the same boat, but sometimes I feel like some of us have already given what the most impactful talk we're going to give, you know, in terms of the most, you know, like C it's hard to live up to C seasoning given the impact that had. But but it was a it was a great keynote. Um it was called Are We There Yet. It was a follow-up to his original keynote from C now, the first one, I think.

ConorYeah, I s I saw in the I think description of the keynote, it said it was a follow-up to BoostCon 2007, which I didn't even realize it went back that far. Maybe maybe I miss I'm misremembering it was 2000.

BenTo 2007, yes. A possible future of software development. That was Sean's keynote uh in 2007.

ConorI wonder if that talk uh because I'm not sure if they go back that far before C now. I know some of the BoostCon talks are online, but I would be surprised if that is even available.

BenYeah. It was very sketchy before about 2014, 2015. That's about as far back as videos go. And even back in those days, that was some of them were before video sponsors.

ConorYeah. I was actually just, was it a week ago or two weeks ago? I can't remember how I found my well way down the rabbit hole, but I ended up trying to watch uh a couple of Bartosz Meluski's really old C now videos, but like it's like a cam recorder stood up, and so depending on the year, it's like the light wash, you can barely make out what's on the screen, and all you see is the shadowy figure with you know Bartosz's crazy haircut. Uh and anyways, not very watchable is the point. So yeah. Anyways, so uh a good talk, but I mean, like you said, C seasoning, hard to hard to live up to.

BenYeah, and I don't think I'll ever live up to you know uh context for all the things again. You never know. You got you got uh a few decades ahead of you, so uh Um yeah, so that was great. Um so who uh uh Sean's keynote, we started off with uh Lisa had the midweek keynote, Lisa Lippingcott. Um and that was uh a really great talk.

ConorI didn't actually realize that was a keynote because it the the title of it made it seem like it was um what was the title? Balancing the books. I thought that was like a uh agenda item similar to the like library of the week. Like we need to take a look at the finances.

BenUh no, no, it was um it was Lisa's uh midweek keynote, and uh she talked about uh she talked about double entry bookkeeping across the function call interface. Uh as uh and it was a really interesting talk and and uh uh I thought very um easy to follow. You know, some of Lisa's talks get quite mathematical, and I'm not although people might think I'm good at maths, I don't have formal math training beyond high school.

BenUm so you know I follow and keep up where I can. But anyway, balancing the books was great. Um it was she was talking about, yeah, so so double entry bookkeeping of of the contract, of the of the rights given to the callie by the caller, and the duties also imposed upon the caller by the callie. Right, and so she presented a way of where where both sides can c hence double entry, both sides can keep a record of uh credits and debits in the rights and duties.

BenUm and uh and it and it gets to something like uh well, it gets to something like borrow checking, you know. Um and it gets to it gets to uh a form of safety, we might say. Uh but I'm I'm really not doing it a good service there. Um you should you should watch the keynote when it comes out.

ConorI was gonna say this sounds like uh a talk that you need to watch in order to fully grasp the uh ideas she's putting forward. Yeah, yeah.

BenSome really some really interesting um interesting ideas in that one. Um and then the final keynote was Jeff Garland's keynote, um where it was Generic programming considered harmful. Now I'm not a fan of the title, because I'm not a fan of I'm not a fan of cliches in titles these days. But the talk was great. I thought the talk was really, really, really good.

ConorIs it is it advocating for what the title says, or is it the opposite? Because a lot of times it's clickbait and then they were bait and switch.

BenUh quite the opposite. Je uh Jeff is Jeff is very uh heavily into generic programming. He's he's you know one of its great practitioners over the years in terms of uh boost libraries and other things. So he wa the the talk the title was really asking the question which the talk answers as as and the answer is no, I think.

ConorI see. Okay, so another one to put on the list. Uh and there was uh I mean a ton of other talks, some that mentioned generic programming, um, yours as well, and I noticed that there was I think four different talks, or maybe only three. There was a couple talks that mentioned dec declarative something.

BenYeah, yeah. So there were I think three. Um yeah. Well, so and they were quite they were quite they turned out to be quite different talks. So one was declarative refactoring for the masses. That was Andy Sofer's talk. And Andy uh is an engineer at Bronto Source, and that he has that company with Matt Kulakundis, and um his talk was about their tool that refactors I I think C, but maybe also C C into Rust.

BenOh wow. I I sadly didn't attend Andy's talk because it was in a time slot where I had to do something else. Um and then the other declarative talk was uh Richard Powell's talk, Techniques for Declarative Programming in C. And that was that was a really that was a really good talk for my money. That was um although again it was in a time slot where I wanted to watch like all of the talks in the time slot. The sign of a good conference. Um but but what was good about Richard's talk, I thought, was that he he he he successfully did what I try and and sometimes succeed in doing but more often fail.

BenHe took kind of more everyday C. So he wasn't talking about super template metaprogramming, like heavy stuff. He was talking about like uh using a WX widgets framework, right, in C ⁇ and just writing applications and showing how to refactor and to refactor the code to make it more declarative in the series of steps. And I thought it was a really nice, really nice talk, really some good learnings from that. You know, because as much as we try to program well, I I I guess I shouldn't say that.

BenLike I like I do I do try decl I do do declarative programming and I do do generic programming as much as I can. Uh but you know I also have to do object-oriented programming and I have to do structured programming and imperative programming as well, right? It's not all one way. Right. Um we have to we have to synthesize them all together. And some you know, because at the end of the day, ever sort of at the bottom of everything, it's all imperative. So and sometimes imperative is the right choice.

ConorUm it's like uh Stepanov in his uh efficient uh programming with components uh A9 series, which I'm now working through after having finished uh from mathematics to generic programming, in like the first couple lectures, he uh he has this little five-minute uh digression on OOP because he's making use of OOP and he's like, listen, listen. You know, they say I'm on record saying I don't like OOP and uh that may or may not be true, but doesn't mean I'm not gonna use it when it's the right tool for the job. Uh and and so yeah, it's uh just because you're a big fan of generic programming, aka Stepanov or yourself, doesn't mean you're not gonna use other paradigms or techniques when it's the right thing to do, right?

BenRight, right. And and the right thing to do is sometimes just the way it is in the code base you're working in, right? Because it's too much to change.

ConorThat's what that's what Tony's one of Tony's big uh things is, right? Is you know the the right style or right formatting is whatever the surrounding code is doing because anything else is just gonna look out of place. Um right.

BenYeah. So yeah, yeah, so my talk was another declarative one. I called it declarative style evolved. Uh uh call back to my 2018 talk about declarative style.

ConorIs this is this a sequel, uh uh unofficial sequel or official sequel?

BenIt's a it's a sequel of sorts, I suppose. Um I don't I don't I don't really know. I was talking about declarative structure as opposed to so if the first talk was talking about um style at the level of individual function calls and function bodies and expressions, then this talk was more talking about the level of APIs. So structuring APIs for a declarative style somewhat, but also recognizing that um well, part of it came from uh or most of it I would say came from the work I do now, which is you know, embedded work, very heavily uh I.O.

Benright? In if if if programs are sort of you can imagine on a balance we have maths on one side and I. Most programs do more maths than I.O. probably. But mo but most programs on embedded, like my work, do uh way more I. You know, it's all about marshalling data between between uh I.O.

Benmodules and things like that. Um there's very very little calculation. Anyway, so that means and also, you know, in embedded, a lot of things are just at the level of the here's a global API. Right. So that was a theme of my talk as well. We've got a global API for doing logging, we've got another global API for doing concurrency, another one for doing uh uh handling errors, right?

ConorThat kind of thing. So when you s when you say declarative APIs, like in my head, the kind of two things that pop up are like you know, the sorted versus sort functions in Python, where one's in place versus out of place, and like other things like fluent APIs or the the builder pattern where you're kind of instead of having a bunch of in-place, you know, uh do this, do that, you can kind of chain some stuff together and then under the hood, like you said, it's a bunch of mutation.

ConorUm is that kind of what you're is is that the right idea, or is it your talk focusing on something different than that?

BenI think my talk was sort of at the at the level above that, where it's like how do you choose which API to use? Because one of the problems one of the recurring problems with particularly with embedded work is you you how do you test it, right? So you you want to be able to use the same API in on the platform as you do in desktop tests, right? Um but the implementation needs to change, right? Because you want to test at the level of the API um and and push down as much platform-specific implementation as possible.

BenAnd that's what this talk uh kind of addressed, you know. So so I can declare uh I can declare at the level of which implementation to use for the API, and and I can push that down as far as possible so that tests as far as much as possible can just use the same API and even the same implementation down to as f as far down as I can push it.

ConorInteresting.

BenSo this does sound like a very different talk than than your first. It was a very different talk. It it covered all kinds of things. One of the surprising sort of conclusions I reached in making the talk was um that I don't think that tests I think tests should be imperative. And actually, after the talk, Kirk Kirk Schupp, um, I was talking to him I think the day after or so, and he said he said, you know, I uh I think that's probably because tet we tests don't compose. We don't compose tests.

BenAnd I I made the point in the talk that tests should be simple enough that you just say arrange, act, assert, right? That's the classic kind of trio of things you do in a test. And you just you if you just have arrange, act, assert, that's imperative. There's no reason to go down a declarative programming route to make that any simpler.

ConorI guess I'm trying to think what do you mean by because when I'm thinking of like the unit test that I have most recently written, definitely there's a statement, an assertion at the end, but usually it's a construction of some input, and then you are doing the act. Which in my case, a lot of the times like it can be well, is it declaratively done? It'll just be, you know, like autoconst uh result equals etc etc, of the input, and then you have your autoconst expected, and then you you assert that those things are equal or whatever property you're checking.

ConorSo I guess when you say tests should be imperative, is that an example of an imperative test? And if so, is it the it's the assertion at the end? Or I guess what's what's the difference between declarative and imperative testing?

BenUh you know, let's not get hung up on trying to define what imperative versus declarative means. But I think tests ought to be short. They ought to be short enough that you can just the test takes up no more than your visual field of view at the distance of your monitor, so d uh tet length of a test ought to be like, you know, less than ten lines. Yeah, I was thinking ten lines is the same the same. And and what tests should not be, we can contrast that with what uh w what tests I I often see, which is which is tests that use mocking frameworks tend to get longer.

BenThey tend to confuse uh arrange with assert because they tr that mocking frameworks invariably do this thing where you set up expectations, and so it's confusing the sort of temporal reasoning about the test. You're you're putting the arrange and the assert in the same place, and then finally you're doing the act. Usually find that when I when when when mocks are used, it does not improve things.

BenI've seen, you know, maybe there's a way to use mocks. Well, if there is, I mostly haven't seen it on teams I've worked in in my career. Um and so I've come to the conclusion that mocks just confuse things. Um in in perhaps trying to make, you know, we can argue whether that's declarative or imperative. But anyway, that style. Um that style I don't like.

ConorYeah, I mean I can get behind that. Um I honestly have never used a mocking framework, and whenever AI recommends me using mocking, I'm like, uh, no, we don't need to do that here. That's not necessary. Um and I used to listen to an Android podcast, and they were always talking about I'm gonna get these wrong for the Android devs that are listening, but it's something like Dager versus Juice versus there's all these dependency injection and mocking frameworks for tests. And I I remember listening to it just being like, what uh why is all that stuff um necessary?

ConorI I guess you in in some cases it is if you're trying to do some like UI testing, you have to set up some some state and whatnot. But I don't know. I guess as a library developer, you very rarely have need for like mocking. And if if someone's telling you that you do um I I don't know, I I would question that.

BenI I agree. At the level of unit tests, what I want is for things to be simple. Things to be so simple that I yeah, you know, I don't need to reach for a framework to to mock out APIs. I just want to test the one function I want to test in that in that test. Yeah. Yeah. Yeah, I totally agree with that. Um mocking frameworks also they this might not be true of all mocking frameworks now, but I think it's certainly still true of the majority, that they they absolutely live for the classical, object-oriented, class hierarchy, virtual function world.

BenRight. Right. Yeah. And and that pushes you down. That sort of makes the the tail wag the dog, right? If your test framework is dictating how you structure your code so that you can test it, then that seems the wrong way around to me. Which is another reason I don't like mocking frameworks.

ConorRight, right. Okay, yeah. I I definitely can stand behind that. Um I can't necessarily say that I've seen all mocking frameworks used poorly or um not optimally, but that's just because I have avoided them. Um have not worked on a team or a library that has to make use of them. We almost always just use unit testing frameworks and yeah, try to write short tests.

BenUm anyway, so there were lots of other good talks. Um Brayden gave a talk, Braden Ganetsky, uh Lambda All the Things, which was a very, a very fun talk where he just he took the idea of um you know, can I make everything from Lambdas? Can I can I make type traits from Lambdas? Can I make can I go down this road? It was a very it was a very nice talk for C ⁇ now because it was a very sort of uh one of these talks that obviously no one would do that in their production code, but it's the sort of talk that's that's a playful talk, a talk that explores an idea and takes it to to even absurd conclusions, but we learn things along the way, right?

BenAnd that's that that in my view is very much the spirit of C now. You know, the the playfulness.

ConorYeah. I mean you've given uh talks like that in your past as well. The the std accumulate uh algorithmic empire does kind of the same thing, right? Um Wait, you thought that was not serious? I think you said as much in the talk.

BenYeah, I uh again, I yes. It was exploring an idea. I tend to do that a lot in lightning talks as well. Um you know, show some show some weird thing. Um and and you know, you and I are both fans of um languages in general, and the the idea that languages embody computational paradigms. Um you know, so so in a sense, you know, C and Java and Python and C sharp, they're all really the same language-ish.

BenThey're all descended from Algol, right? But then something like Lisp or Smalltalk or Prologue, they are different, they are qualitatively different, they're different families, right? And so uh sometimes I think about languages like I have a sort of term that I use where it's it's everything is an X language. Is it is this language and everything is an X language? You know, C is not, but like scheme is everything's an S expression, everything's an expression, right?

BenUm is, everything's a table, right? Prologue, everything's a clause. Um those kind of languages which really lean heavily onto one idea and just see how far they can take it. And in many cases, they can take it so far as to be to be a completely uh kind of programming complete programming paradigm.

ConorThere's some quote, and this is where I wish I was better at uh I had a friend, Adam, who always knew the aphorism or witticism for the moment. He always just had on top of mind, but there's some quote or aphorism that's you know, constraint breeds innovation or something like that. Um that is uh basically what you're talking about there, that you know, limit what you're allowed to do, and then you come up with a novel solution that would have seemed impossible, or you know, you never would have explored in that direction because you've got other paths available, right?

ConorRight, right. Any other talks worth uh mentioning while we're winding down the C now recap?

BenThere were there were lots of other good talks. Um Dietmar Kuhl gave a talk on called Getting the Lazy Task Done, and that was about another talk about senders and receivers and their application. Um in that case, their application to coroutines uh was the topic, I believe. Yes. And uh Zach gave a good talk about about writing std compatible views. Um and then a talk I didn't get to go to was Steve Downey's talk, um which I will make sure to catch as soon as it comes out.

BenBuilding streams out of hot air. Ooh, that's a catchy title. Umsing senders and receivers to build streams in the style of SICP in the sense that, you know, I think it's about lecture five or so where the where they show that, you know, what you thought uh what you thought of as data really doesn't have to be data under the hood, it can just be made of functions. Right. And so I think Steve's talk went down the similar vein, although I didn't get to see it in person because it was, you know, in one of those talk slots where there was a lot.

ConorRight, right, right. I'm trying to think, yes, I remember that part, and they have a number of exercises where you are calculating the next, you know, number. I can't remember if Ramanujan was one of them. Um but uh Yeah.

BenIt's a common Yeah, in in learning functional languages, that's a common exercise as you get toward the intermediate level of like the lazy stream, the infinite stream. And then you know you can start out with like an infinite iota stream, and then you can of course famously you can do the Civil Eratosthenes to to filter out you just take the head of the stream, you start the stream with two, you take the head and you filter out that, and then you take the head of that stream, filter out the next, you end up filtering out all of the multiples of primes.

ConorYes. A very nice implementation of uh Yeah, what can be well not hairy necessarily, but it's you know, if you look at the different implementations, technically you're supposed to start at what is it, two or three and and do some first pass for efficiency, but uh you can just build that one up very, very quickly. Okay. Well, all of the talks and the talks we didn't mention. I'm sure that there was more than uh Ben could mention.

BenI'm sure I forgot several that I'll kick myself for not mentioning, but we can't mention them all though.

ConorThere's uh there's m there's uh way too many. But uh links to all of them, like I said, will be in the the show notes. Um they probably will all be quote unquote unlinked for the next uh period of time. But yeah, if you're listening to this in the future, um they probably will be updated. So uh yeah, C now in the books. I'm not sure. What's the next it might be C on C? Yeah, I know that one's at the typically it's at the tail end of June. And then CPP North is in July.

ConorYep. And then I think that brings us to CPP con. There might be, I know actually there was I think it might have already taken place. There was a virtual C. I was gonna say C under the sea is somewhere in there as well, right? That one was October last year, and my guess I actually know, I think I know it's the same roughly the same time. So I think it's in October sometime. And yeah, there there's a bunch of other ones. I mean, I know meeting C is in is in November as well as Code Dive.

BenUh pure virtual C, which I think you were about to say before. The one the one day Microsoft online conference, that yeah, that happened during the week of C now, I believe. It was I think it was April 30th. Oh, that's uh that's poor timing. Uh it was the same last year. Oh, was it? Last year, yeah, 2024. Um yes, and I had to record my talk. Cy brand reached out to me and they said, Would you like to give a talk at Pure Virtual C?

BenBecause um CI I think they originated the conference, or they were certainly a driving force for putting it on. Um and uh Yeah, so so and it and it again it fell during C now, so I recorded my talk ahead of time and and submitted or sent it off. So then I was at one conference able to attend another, I guess.

ConorA copy of you was uh speaking at another conference uh for some definition of the word copy. Yeah, I I I don't think I saw any of the talks from this year, but um yeah, we'll link in the show notes. There's there's tons we live in that's one of the best parts about C is that we uh there's a cornucopia of content in the form, not just of lectures, but um podcasts, blog posts, um, which is can't be said of all communities. Um and as someone who likes to ingest as much of that kind of stuff as possible. Yeah, it's great to be able to watch this stuff.

ConorUh all right. I mean we should maybe put a bow on the C now 2025 recap and transition. That was what, episode two thirty four? Be sure to check these show notes either in your podcast app or at adspthepodcast.com for links to anything we mentioned in today's episode, as well as a link to a GitHub discussion where you can leave thoughts, comments, and questions. Thanks for listening. We hope you enjoyed and have a great day. I am the anti price. Um

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Episode 313: C++26 Reflection vs CRTP, AI, Kids & More with Zach Laine

    Nov 20, 202647 minAudio

    In this episode, Conor and Bryce chat with Zach Laine about C++26 Reflection vs CRTP, AI, kids & more. Link to Episode 313 on Website Discuss this episode, leave a comment, or ask a question (on GitHub) Socials ADSP:...

    • Apple Podcasts

    Credit the people on this episode

  2. Episode 312: The C++26 Contracts Fiasco

    Nov 13, 202652 minAudio

    In this episode, Conor and Bryce chat with Zach Laine about the C++26 contracts fiasco. Link to Episode 312 on Website Discuss this episode, leave a comment, or ask a question (on GitHub) Socials ADSP: The Podcast:...

    • Apple Podcasts

    Credit the people on this episode

  3. Episode 311: Career Changes, GPUs & More with Zach Laine

    Nov 6, 202628 minAudio

    In this episode, Conor and Bryce talk with Zach Laine about his career and the career changes he has made. Link to Episode 311 on Website Discuss this episode, leave a comment, or ask a question (on GitHub) Socials...

    • Apple Podcasts

    Credit the people on this episode

  4. Episode 310: Leaving NVIDIA for... ?

    Oct 30, 202624 minAudio

    In this episode, Conor and Bryce talk about Bryce's next chapter and where he is leaving NVIDIA for. Link to Episode 310 on Website Discuss this episode, leave a comment, or ask a question (on GitHub) Socials ADSP: The...

    • Apple Podcasts

    Credit the people on this episode

  5. Episode 309: Default Construction & CppCon 2026 with Jason Turner

    Oct 23, 202629 minAudio

    In this episode, Conor and Ben chat with Jason Turner about default construction in C++. Link to Episode 309 on Website Discuss this episode, leave a comment, or ask a question (on GitHub) Socials ADSP: The Podcast:...

    • Apple Podcasts

    Credit the people on this episode