@[email protected] to Programmer [email protected]English • 3 months agoDebugginglemmy.dbzer0.comimagemessage-square44fedilinkarrow-up1913
arrow-up1913imageDebugginglemmy.dbzer0.com@[email protected] to Programmer [email protected]English • 3 months agomessage-square44fedilink
minus-square@[email protected]linkfedilink2•edit-22 months agoEven if you’re not using one, you should be instinctively looking for a semicolon the moment you get a syntax error unless you’re a complete beginner.
“oh it was just a missing semicolon”
Linter issue.
Even if you’re not using one, you should be instinctively looking for a semicolon the moment you get a syntax error unless you’re a complete beginner.
Rubber duck debugging often helps.