Відео

simple and beautiful

@20:00 i agree w/ guy#2

C+++

That giggle/laughter at 1:59 makes the video worth watching, even besides the awesome explanation :D

Best explanation I have heard of !

Awesome explanation!

❤️

00:00:00 Introduction 00:00:30 Panel Introductions 00:06:45 Are C lambdas in the works? 00:07:04 JM's response 00:10:00 OM's response 00:10:42 RS's response 00:11:47 JM's response 00:13:15 Are you able to declare (non-lambda) functions inside functions in C? 00:13:20 JM's response 00:14:12 With C23, is C diverging from C++? 00:15:15 JM's response 00:19:04 OM's response 00:20:16 Is there a similar three-year cycle in the C standards committee? 00:20:35 RS's response 00:22:43 How to handle C23 #embed versus C++ constexpr? 00:23:27 Why should I use C instead of Rust or Go for new projects? 00:24:00 OM's response 00:25:50 RS's response 00:26:36 JR's response 00:26:55 Is C the most portable language right now? 00:26:57 JM's response 00:31:01 What is the state-of-the-art in fuzzing compilers and standard libraries? 00:31:25 JR's response 00:34:55 Are the compiler and standard library vendors good as fuzzing their own stuff? 00:35:22 JR's response 00:35:57 (P)eter: Comment about languages with a specification allows for certification. 00:36:53 OM's response 00:37:28 JM's reponse 00:43:05 If you start using 'unsafe' in Rust, why do you need Rust? Why not use C instead? 00:44:20 JM's response 00:48:08 JR's response 00:48:59 RS's response 00:49:28 What is C's biggest mis-feature in your opinion? 00:49:45 RS: realloc() 00:51:40 OM: C99 00:52:45 JR: Order evaluation of parameter lists 00:53:26 JM: Rant about order evaluation in C/C++ 00:58:40 JT: Rant about C++17 funcation argument evaluation bugs in GCC compiler 00:59:12 P: Defending the right-to-left order evaluation 01:00:55 JM: On Peter's assert() proposal to C standards committee 01:02:00 What are your favorite feature(s) in C23? 01:02:50 JM: memset_explicit() 01:05:16 JM: Attributes 01:06:15 RS: Elimination of trigraphs 01:07:15 RS: Attributes 01:08:26 RS: Checked integers 01:09:50 JT: #embed 01:09:58 JM: #embed 01:17:15 OM: memset_explicit() 01:17:32 What is the problem with memset()? 01:17:41 OM's response 01:19:01 Now that C23 has checked integers, would there be room for a specific limited form of operator overloading in order to not make them obnoxious? 01:19:17 RS's response 01:21:03 JR's response 01:22:22 JM's response 01:27:01 Wrap up

Maybe hide wacky evaluation order behind atributes?

When Jason asked me what my role was in Seaworld I should have said "Orca".

On the subject of "why use C in a new project?" I'm actually seeing that C is becoming sexy again as the language for universal interoperability. With the rising popularity of languages like Swift, Go, Rust, etc which can all interop natively with C, using C++ at very least at the API boundary is becoming less desirable. People are discovering that its a dead-end in terms of interoping with other languages. You can see an extreme example of using C for this kind of interoperability in the GNOME stack and GTk. They have a purely C-based object oriented type system, which has enabled GTk and the rest of the stack to bind to virtually every language out there and is why it's so ubiquitous in terms of language support.

#embed discussion begins at 1:09:40. Order of operations "rant" 53:25

Thank you for uploading this! It is slightly outdated tho, value categories were again changed in C++17-you can not longer move from prvalues, for example.

'promo sm' 👇