• Home
  • Technology
  • Gaming
  • Entertainment
  • World & Business
  • Science
  • Sports
  • AI
HomeTechnologyGamingEntertainmentWorld & BusinessScienceSportsAI
  • HomeTechnologyGamingEntertainmentWorld & BusinessScienceSportsAI
    • Home
    • Technology
    • Gaming
    • Entertainment
    • World & Business
    • Science
    • Sports
    • AI
    AI
    Reaction

    A critique of LLM-generated code's heap allocation habits

    A user argues that pretraining on mediocre code leaves habits that post-training cannot entirely erase.

    MP
    1 Source, 11h ago, first seen 11h ago

    TLDR

    A user argues that LLMs retain coding habits from mediocre pretraining examples despite post-training. They say they run extra critique-loop iterations to clean up heap allocations they consider unnecessary.

    Combined views

    12K

    1 Source, first seen 11h ago

    likes

    Combined views

    12K

    1 Source, first seen 11h ago

    141 likes
    141
    23 comments
    24 saves
    3 reposts
    Featured Source
    23 comments
    24 saves
    3 reposts

    Sentiment

    Positive——Negative

    Summary

    Not enough discussion yet.

    No sentiment analysis available yet.

    Sentiment

    Positive——Negative

    Summary

    Not enough discussion yet.

    No sentiment analysis available yet.

    Today's Rank

    —

    Not ranked yet

    Today's Rank

    —

    Not ranked yet

    1 Source

    @MParakhinLLMs are biased by pretraining on mediocre code. Post-training helps, but the horns are still visible. I am always triggered by using heap allocation when it is not needed (including std::optional/Option) - running special critique loop iterations every time to clean up...11h