No post body was provided.
Ask HN: Why do AI code editors suck at closing tags?
1–7 of 7 posts
Re: Ask HN: Why do AI code editors suck at closing tags?
#2Context favors the newst tokens. To get closing tages means to find much older tags.
HTML is simply oppositive with LLMs favoring the next token based on the just made.
Re: Ask HN: Why do AI code editors suck at closing tags?
#3[dead]
Re: Ask HN: Why do AI code editors suck at closing tags?
#4Context favors the newst tokens. To get closing tages means to find much older tags. HTML is simply oppositive with LLMs favoring the next token based on the just made.
There must be some interface for LLMs tocdeal directly with the tree structure of programming and computer languages. Like, something similar to Emacs paredit interface, but for arbitrary languages
Re: Ask HN: Why do AI code editors suck at closing tags?
#5They don't. Use better tools
Re: Ask HN: Why do AI code editors suck at closing tags?
#6Never encountered this issue until I tested GLM and Kimi K2 models.
Opus and Sonnet seems to be good at handling this, even when giving them a code with open tags, they'll know where to put the closing tag quickly.
Re: Ask HN: Why do AI code editors suck at closing tags?
#7Same reason they can't count the 'r's in "strawberry", these models don't actually understand structure, they just autocomplete really convincingly.