Here’s an interesting post from an industry legend on exceptions https://www.linkedin.com/posts/bjarnestroustrup_c-exceptions-for-smaller-firmware-khalil-activity-7243244721911865344-J7yy?utm_source=share&utm_medium=member_ios
If the linked in post isn’t readily accessible the underlying talk he comments on is here https://youtu.be/bY2FlayomlE For those without access, Stroustrup says “ Here is a splendid talk from CppCon: https://lnkd.in/eXMrVBKA It’s long and goes into great technical detail of implementation and use patterns but the essence is: * Using C++ exceptions you can get cleaner, more maintainable, smaller and faster code than if you use explicit error codes. You can do so even for tiny embedded systems. This is backed up with impressive numbers. * The current C++ exception handling implementations are appallingly bad. If you are on and ARM using Clang, you can download a library with a much better implementation (a GCC version is in the works). And it’s free.” Not saying Go SHOULD add exceptions but reading others opinions on error handling is always worthwhile. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/61ECC5C8-3A3E-49F6-8D8C-150FABF5A15C%40ix.netcom.com.
