Sjmarf@sh.itjust.works to Programming Horror@programming.dev · 12 days agomallocPlusAIsh.itjust.worksimagemessage-square32fedilinkarrow-up1251arrow-down12
arrow-up1249arrow-down1imagemallocPlusAIsh.itjust.worksSjmarf@sh.itjust.works to Programming Horror@programming.dev · 12 days agomessage-square32fedilink
minus-squarezaphod@sopuli.xyzlinkfedilinkarrow-up14arrow-down1·12 days agoYou don’t need to cast the return value from malloc.
minus-squarevrighter@discuss.tchncs.delinkfedilinkarrow-up1·10 days agothat is besides the point. You can still call malloc, it will still return void*, and it would still reqoire casting in c++
minus-squareaddie@feddit.uklinkfedilinkarrow-up11arrow-down1·12 days agoTrue. Although given how easy it is to cast void pointers to the wrong damn thing, it would be nice if you did, makes refactoring much easier. Makes me appreciate std::any all the more.
minus-squareembed_me@programming.devlinkfedilinkarrow-up3·edit-210 days agoVoid pointer should be avoided anyways. Even I find them rare and I mostly work in embedded RTOS
minus-squareSubverb@lemmy.worldlinkfedilinkarrow-up6·edit-211 days agoThis isn’t malloc though. I have to assume the cast is because the user has experience with the output from an LLM being untrustworthy.
You don’t need to cast the return value from malloc.
you do in c++, no?
In c++ you should use
new.that is besides the point. You can still call malloc, it will still return void*, and it would still reqoire casting in c++
True. Although given how easy it is to cast void pointers to the wrong damn thing, it would be nice if you did, makes refactoring much easier. Makes me appreciate
std::anyall the more.Void pointer should be avoided anyways. Even I find them rare and I mostly work in embedded RTOS
This isn’t malloc though. I have to assume the cast is because the user has experience with the output from an LLM being untrustworthy.