You're not wrong there. The late stage (compilation wise) of template instantiation doesn't help either, as so much context has been built up. The art of debugging C++ compiler output is knowing which 90% to ignore. If you read it all you'll simply go mad.
Concepts at least tells you which criteria you didn't satisfy (as long as the concept is correct...), which - admittedly - feels like putting a bandaid on bullet wound.
Great news! As someone who's moving back to a C++ job after having worked with Rust for several years now, the error message parsing is one of the things I've been dreading the most... I'm still dreading it, but now sliiightly less.
Also, that interactive `-fanalyze`-output with the pointer visualisation looks super handy!
Happy to see there's still focus on the DX in GCC. C and C++ sorely needs it.
Bambu showed their true colours last year when they would've eliminated offline access altogether if not for public outrage. You don't own your Bambu printer, you're leasing it at a subsidised premium.
This move does not surprise me at all, and I'm genuinely happy that Louis is willing to shell out money to help those that can't defend themselves.
I'm happy that Bambu finally made Prusa care, but I will not cheer them even if they consistently innovate. It's just sad.
Thumbs up for both of them, but I must say that DeltaHedra has become my new favourite FreeCAD content creator. Especially after he started using his own voice. His old content was good, but his current his magnifique! The quality of the content he pushes is above and beyond.
LinkedIn is a masquerade ball dressed up as a business oriented forum. Nobody is showing their true selves, everyone is either grinding at their latest unicorn potential with their LLM BFF or posting a "thoughtful" story that is 100% totally real about a life changing event that somehow turns into a sales pitch at the end...
I am quite obviously blind, but I still stand by my sentiment. I would rather have a "bad" but honest PR body than a machine translated one where the author isn't sure about what it says. How will you know if what it says is what you meant?
This seems fair, tbh. And I fully agree on the policy for issues/discussions/PRs.
I know there will probably be a whole host of people from non-English-speaking countries who will complain that they are only using AI to translate because English is not their first (or maybe even second) language. To those I will just say: I would much rather read your non-native English, knowing you put thought and care into what you wrote, rather than reading an AIs (poor) interpretation of what you hoped to convey.
I switched to AeroSpace from Yabai because I had to disable parts of SIP for certain functions (such as switching workspaces with keybindings from SKHD), and that didn't feel right. Updates are also smoother since I don't need to update the sudoers file allowing the Yabai CLI to run without requiring password. Been happy as a clam ever since.
Same as a friend of mine who works for NAV. There's a whole lot of long-ass variable and function names because they use the Norwegian name for whatever they are calculating. It makes sense for them though, as the ones who review your code are lawyers...
Concepts at least tells you which criteria you didn't satisfy (as long as the concept is correct...), which - admittedly - feels like putting a bandaid on bullet wound.