Alex Vergara

> On slide 74 in https://github.com/CppCon/CppCon2022/blob/main/Presentations/CppCon-2022-Sutter.pdf we have the example of initialization safety by naming the return values already in the definition > > ``` > f:() -> (i: int,...

@jcanizales that's a better interpretation that my explanation, thanks for it 👍 Even tho, mixing the best of both worlds, ommiting the `return` statement could be an optional syntax, for...

> > I would vote for that. The same rule for all types. No special cases. So either `unsigned long int` is a type and therefore `unsigned long UserType` is...

> > > I think there is a 3rd option: Make the proc-macro return something like > > ```rust > syn::Error::new(self.meta.span(), format!( > "Expected valid identifier, found `{name}`. Diesel automatically...

> example from video: https://compiler-explorer.com/z/nncG6EaqW For those who wants to use `Clang` to play with the example, actually the syntax must be ``` template typename ``` Clang refused to support...

> I've been having the same inconvenience, if you want to use `stow` or any similar tool for multiple machines, you can't use the same path for all machines. The...

@williamboman Are there any updates on this? I use a Manjaro distro, and two different Windows from Monday to Friday. Everything runs nice on Linux, but in Windows I am...

> Perhaps this could be "fixed" by adding an optional callback to the Mason API somewhere that triggers when a utility fails to install (or when the required libraries are...

> I agree that the `return;` should be implicit. Added to the near-term to-do list! (roughly: look at over the holidays) Programmer holidays are just a mith! I am glad...

> Looks like you need to specify the standard in CMake file explicitly instead of just on the compiler pane. Like so: https://godbolt.org/z/f9eKWEn84 So finally, is needed to use a...