ameliaquining

6 ms·

91.
by ameliaquining 2mo ago
If I were doing this, and the code generator was itself in Python, I'd probably use ast and/or tokenize to avoid having to manipulate literal whitespace.
92.
by ameliaquining 2mo ago
Python's significant indentation does have real costs, but they mostly don't affect experienced programmers working on real codebases in real editors or IDEs. Rather, they are things like, it makes the REPL more cumbersome, and ne
93.
by ameliaquining 2mo ago
Haskell's significant indentation is, in my experience, much worse than Python's at fading into the background by matching what you would have done anyway.
94.
by ameliaquining 2mo ago
The article doesn't provide any support for the assertion that keeping the source code unreleased makes a bigger difference re: quantity of unwanted inbound communication than closing the conventional issue and PR channels. It instead
95.
by ameliaquining 2mo ago
For what purpose? Different use cases require different language features.
96.
by ameliaquining 2mo ago
Go doesn't have any kind of story for incremental migration from C++ or Java; you are talking about rewriting all those codebases from scratch, which is an obvious nonstarter as long as engineering resources are finite. IIUC Fuchsia us
97.
by ameliaquining 2mo ago
Sorry, what exactly is your disagreement with the SO answer? It doesn't mention the reals.
98.
by ameliaquining 2mo ago
Minor factual correction: The Codex client is open source. https://github.com/openai/codex
99.
by ameliaquining 2mo ago
I guess my view is that it's right and proper for people to point out invalid arguments, even if they're being made to justify something that the author has the right to do anyway.
100.
by ameliaquining 2mo ago
Note, though, that disabling PRs in particular is only a couple months old (and was prompted by the current wave of consternation around AI-assisted contributions). Before that you had to set up a bot that would just auto-close them and it
101.
by ameliaquining 2mo ago
Do you reject the paper's claim (that disparate impact liability makes almost everything presumptively illegal, including in situations where no one has done anything wrong), or do you think that there's no way to address plausibl
102.
by ameliaquining 2mo ago
No, I'm saying that you're conflating current LLMs with future ones. The 2018 date was an indication that Musk wasn't referring to any specific already-existing LLM, since there were no LLMs in 2018.
103.
by ameliaquining 2mo ago
Most users of coding agents do want the agent to edit their code, and don't want to have to click something before every edit. If you want something different, that's why it's a setting.
104.
by ameliaquining 2mo ago
Leaving aside any questions of Musk's credibility, he was not referring to any existing LLM, as should be evident from the 2018 date in the URL.
105.
by ameliaquining 2mo ago
Announcement post is https://claude.com/blog/auto-mode-default-in-claude-code , link should probably point there instead of the tweet.
106.
by ameliaquining 2mo ago
Nobody is claiming that any currently-existing LLM is more dangerous than nuclear weapons.
107.
by ameliaquining 2mo ago
Well, yeah, I would not expect indexing (on the standard library types) to be usable within a no-panic function, because panicking on out-of-range inputs is what those operations do. Admittedly, probably lots of people would initially think
108.
by ameliaquining 2mo ago
Pretend for a moment, then, that I've never worked in a unionized industry and everything I know about unions is from the media environment that you say is untrustworthy. I think it would be very helpful, in that case, to write the few
109.
by ameliaquining 2mo ago
Was it this one? https://docs.google.com/spreadsheets/d/e/2PACX-1vRPiprOaC3Hs...
110.
by ameliaquining 2mo ago
Cloudflare OS does have the important risk-mitigating feature that you can fork it if the vendor becomes hostile to your interests. You can't really do that with managed services like Workers (workerd exists but isn't a drop-in re
111.
by ameliaquining 2mo ago
It's actually quite straightforward to write a TryFrom impl that returns Err if the conversion fails (i.e., if the input floating-point value is infinite, NaN, or out of range of the target integer type). The reason this hasn't be
112.
by ameliaquining 2mo ago
How do you know?
113.
by ameliaquining 2mo ago
Nitpick: Rust doesn't panic in this situation, it saturates (i.e., returns the largest possible value for the given integer type). Among other reasons, because a lot of existing programs that triggered this UB happened to work in pract
114.
by ameliaquining 2mo ago
You really think the big American labs are distilling each other? That surprises me.
115.
by ameliaquining 2mo ago
Out of curiosity, is there some reason it would be harder than I'm imagining? It seems like a fairly straightforward type-system feature. (I.e., it would be a lot of work, but only because any significant new language feature is a lot
116.
by ameliaquining 2mo ago
I had read that post, but IIUC it doesn't address the kind of backcompat issues that I meant to be referring to (the ones that would apply even if there was only ever going to be one new question-mark trait).
117.
by ameliaquining 2mo ago
My sense of sentiment in the project right now is that people want to keep the invariant that assignment (to an ordinary memory location) is always just a memcpy and never calls arbitrary user-defined code, because if that code does somethi
118.
by ameliaquining 2mo ago
The people working on this are aware that it poses backcompat problems that don't have obvious solutions. They are looking into non-obvious solutions. https://lcnr.de/blog/2025/11/28/implicit-auto-tr
119.
by ameliaquining 2mo ago
We already have a Vec<T> whose size can't change, it is called Box<[T]>. So Vec doesn't need to support !Move types.
120.
by ameliaquining 2mo ago
This is not currently a project goal. As with many things in the Rust project, it could be, if someone wanted to step up and dedicate the required engineering resources.

More ›