Sivecano@lemmy.dbzer0.com to 196@lemmy.world · 2 years agocoming here was a trap, but I shall obligelemmy.dbzer0.comimagemessage-square8fedilinkarrow-up1116arrow-down14
arrow-up1112arrow-down1imagecoming here was a trap, but I shall obligelemmy.dbzer0.comSivecano@lemmy.dbzer0.com to 196@lemmy.world · 2 years agomessage-square8fedilink
minus-squareperviouslyiner@lemm.eelinkfedilinkEnglisharrow-up25arrow-down1·2 years 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·2 years 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·2 years agoAlthough that’s gotten better in recent years, as I recall.
minus-squareSivecano@lemmy.dbzer0.comOPlinkfedilinkarrow-up2·2 years agoyeah, think so too. at least with some standard library stuff.
minus-squareChais@sh.itjust.workslinkfedilinkarrow-up2·2 years agoIsn’t that mostly a matter for the compiler?
minus-squareSivecano@lemmy.dbzer0.comOPlinkfedilinkarrow-up1·2 years 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