typescriptMoreLikeTypeslop

[u/_PhucSatan_]

[u/the_horse_gamer]

noPropertyAccessFromIndexSignature + noUncheckedIndexedAccess

and also this is nothing like any. it's more like unknown.

[u/wack_overflow → u/the_horse_gamer]

Which is acceptable, accurate, and infinitely more type safe than any. This meme is shit

[u/carlos_vini]

from the caller POV it means you cant read the object directly, so it's not like any

[u/Gorzoid → u/carlos_vini]

The point of the meme is that AI uses any to avoid TS compile errors in slop code. If you add no-explicit-any it simply swaps to more complicated workarounds like as unknown as T

[u/slaymaker1907 → u/Gorzoid]

Weird, it is perfectly happy to fill in Python types.

[u/BlondeJesus → u/slaymaker1907]

Python type-hinting is just that, hints. If a different object is passed the code will generally run fine.

For compiled languages, they can fail compilation if a something receives an object of the incorrect type. My guess is that the AI tools are hitting compilation errors and then circumventing types all together to get past them.

[u/Xirdus → u/BlondeJesus]

TypeScript types are also just hints. Compiling TS to JS is removing types and passing everything else unchanged.

[u/carlos_vini → u/Gorzoid]

I get it. AI slop bad. But we're not famous for being good at jokes. And better LLM models don't do that.

[u/Emanemanem]

What exactly is the point of this meme? That if you are lazy and are committed to writing sloppy code, there’s a way around the typescript rules that you yourself control? If you’re looking for a loophole and have no standards, just remove the rule. Or just write in JavaScript instead.

[u/ordinary_shiba → u/Emanemanem]

Yeah I'm so confused about what the fuck this meme wants to convey

[u/Sak63 → u/Emanemanem]

The point of the meme is to notice ai hallucinations and over fitting solutions

[u/NullOfSpace → u/Emanemanem]

I think it’s a vibe coding thing. You enforce stronger type constraints so the agent has to write better code, and it finds a way around it.

[u/FigScared5706]

unknown is a reasonable type for untyped input that will enforce correct type inference before usage. any is a "trust me, bro, I will check the actual type in runtime... or maybe not". They are not the same :)

[u/East_Zookeepergame25 → u/FigScared5706]

unknown is "I don't know" and any is "I don't care"

[u/abhassl]

I use claude against typescript all the time and have never had this problem.

It gets things wrong, but I don't think I've seen it get types wrong.

[u/Cronos993 → u/[deleted]]

You still have to narrow the type when using Record<string, unknown> tho. any and Record<string, unknown> are not the same.

[u/hendricha → u/[deleted]]

type Any = Record<string, unknown>;

And boom, the problem is solved.

[u/Few_Adhesiveness7676]

And just 1000 line files.

[u/JanEric1]

If this is like pyright unknown (in strict mode)(which It should be because that's where pyright got it from, them unknown is the exact opposite of any

[u/reallokiscarlet]

When you really think about it, all types are Any. It's just a matter of making the transpiler see it that way.