Sivecano@lemmy.dbzer0.com to 195@lemmy.world · 11 months agocoming here was a trap, but I shall obligelemmy.dbzer0.comimagemessage-square8fedilinkarrow-up1114arrow-down14
arrow-up1110arrow-down1imagecoming here was a trap, but I shall obligelemmy.dbzer0.comSivecano@lemmy.dbzer0.com to 195@lemmy.world · 11 months agomessage-square8fedilink
minus-squareperviouslyiner@lemm.eelinkfedilinkEnglisharrow-up25arrow-down1·11 months ago“Here is the source of your error” (points to a template definition 15 levels deep in the standard library)
minus-squareSivecano@lemmy.dbzer0.comOPlinkfedilinkarrow-up13arrow-down1·11 months ago“error on line” (points to syntactically perfectly fine line of code until you realize, that you forgot to add the semicolon after your macro on the previous line)
minus-squareChais@sh.itjust.workslinkfedilinkarrow-up2·11 months agoAlthough that’s gotten better in recent years, as I recall.
minus-squareSivecano@lemmy.dbzer0.comOPlinkfedilinkarrow-up2·11 months agoyeah, think so too. at least with some standard library stuff.
minus-squareChais@sh.itjust.workslinkfedilinkarrow-up2·11 months agoIsn’t that mostly a matter for the compiler?
minus-squareSivecano@lemmy.dbzer0.comOPlinkfedilinkarrow-up1·11 months agoYes, but I’m not sure how good the compiler is with arbitrary macros as opposed to the stdlib ones.
“Here is the source of your error” (points to a template definition 15 levels deep in the standard library)
“error on line” (points to syntactically perfectly fine line of code until you realize, that you forgot to add the semicolon after your macro on the previous line)
Although that’s gotten better in recent years, as I recall.
yeah, think so too. at least with some standard library stuff.
Isn’t that mostly a matter for the compiler?
Yes, but I’m not sure how good the compiler is with arbitrary macros as opposed to the stdlib ones.
deleted by creator