aw1621107

7 ms·

61.
by aw1621107 2mo ago
> apparently that isn't an issue on JS, Java and .NET JITs in adopting more modern architectures. I think it'd be an issue irrespective of the architecture? Optimizations are generally expected to preserve semantics and those l
62.
by aw1621107 2mo ago
What makes you think the author is "advocating for planned obsolescence"?
63.
by aw1621107 2mo ago
> Rust's signed arithmetic is fully specified to wrap around. Well, kind of. It's currently documented to wrap in release mode by default , but it's just that - a default. You're free to enable overflow checks in rel
64.
by aw1621107 2mo ago
> Because it imagines that no library other than libc has an ABI that depends on intmax_t. I don't get quite the same impression. The sense I get is more that such a change would basically need to happen "bottom-up": >
65.
by aw1621107 2mo ago
I think the most recent revision of the proposal basically says it not helping for such use cases is intentional? e.g., from Section 4.4.1. Standard Library Redeclaration [0]: > Thankfully, we are not particularly concerned about the abi
66.
by aw1621107 2mo ago
How so?
67.
by aw1621107 2mo ago
I think that's somewhat overly reductive. A significant portion (maybe 1/3-1/2?) of the article is devoted to describing mechanisms by which an ABI could be evolved, including a new (?) mechanism implemented in the author&#x2
68.
by aw1621107 2mo ago
Previous submissions with comments: - 2023-06-10, 64 points, 16 comments: ( https://news.ycombinator.com/item?id=36249253 ) - 2022-03-13, 175 points, 129 comments: ( https://news.ycombinator.com/item?id=3066052
69.
by aw1621107 2mo ago
For a bit of context, this is the basis of what the Rust devs would eventually call Polonius. This first iteration didn't quite pan out, but the devs eventually developed a new version [0] that seems to have worked out to the point tha
70.
by aw1621107 2mo ago
Huh, that does sound like quite the grab bag of features. Think I'll have to find time to further investigate. Thanks for taking the time to elaborate!
71.
by aw1621107 2mo ago
The changes to std::string were made because "the [pre-C++11] definition of basic_string allows only very limited concurrent access to strings. Such limited concurrency will inhibit performance in multi-threaded applications." The
72.
by aw1621107 2mo ago
What favorite feature(s) do you miss when working in other languages?
73.
by aw1621107 2mo ago
Oh, that is certainly not what I was expecting at all. I stand corrected! I do have to wonder though - do you know what proportion of the C++ compiler time is spent parsing your generated C++ code vs. optimizing it?
74.
by aw1621107 2mo ago
Oh, true! That's on me for not being specific enough. I was thinking about the optimization pipeline.
75.
by aw1621107 2mo ago
> Not for C++ code generated by whole program optimizing compilers. I'd be quite surprised if an optimizing compiler generated C++ code somewhere in its pipeline!
76.
by aw1621107 3mo ago
Related: HN post for original article on 2023-02-28 ( https://news.ycombinator.com/item?id=34966137 ), 739 points, 914 comments Discussion between Casey (author of this article) and Uncle Bob (author of _Clean Code_, whose pr
77.
by aw1621107 3mo ago
I think you might be misreading GP? They're basically agreeing with GGP ("so hopefully this gets sent to the sausage factory as well"); they're just saying that the process of actually changing the standard to remove (th
78.
by aw1621107 3mo ago
You never know if the person on the other end is going to be one of today's lucky 10000 :P
79.
by aw1621107 3mo ago
At the time Herb made that comment GSL was documented as supporting XCode 12.5.1/13.2.1, GCC 10/11, Clang 11/12, and Visual Studio 2019/2022 using both MSVC/LLVM [0]. Even if MSVC had special support for GSL I'
80.
by aw1621107 3mo ago
> An alternative way to "forget" a value is to hand it off to another thread that then loops infinitely. Might be able to address that by only allowing such a handoff to a thread spawned via some scoped abstraction to ensure th
81.
by aw1621107 3mo ago
> what exactly makes the best performing languages perform so There's a multitude of factors. Broadly speaking, to achieve high performance on modern hardware you want one or more of: - Control over emitted code and/or data str
82.
by aw1621107 3mo ago
I don't think Discord counts as a data broker under the act as it does not apply to entities with whom you have a "direct relationship"
83.
by aw1621107 3mo ago
To the extent that implementations promise, sure. But that is beyond the scope of the standard.
84.
by aw1621107 3mo ago
This comment [0] from dang might be relevant: > In case it's of interest, here's the standard language from emails I send people: > We try not to delete posts that got replies, because doing so would be unfair to the other c
85.
by aw1621107 3mo ago
Only if HN counts as a "data broker" under the corresponding law [0]. It states: > “Data broker” means a business that knowingly collects and sells to third parties the personal information of a consumer with whom the business
86.
by aw1621107 3mo ago
I think it's meant to be parsed as "I liked being able to (express (calling external libraries))", not "I liked being able to (express calling) (external libraries)"
87.
by aw1621107 3mo ago
> It also means that the behavior needs to be stable across time I don't think IB has to be stable over time? For instance, whether and which extended integer types exist is IB and that has definitely changed over time. > and t
88.
by aw1621107 3mo ago
There's always unspecified behavior if documentation is considered to be too onerous.
89.
by aw1621107 3mo ago
> They made it undefined intending to encompass all of these. Why wouldn't implementation-defined behavior suffice in this case?
90.
by aw1621107 3mo ago
I think GP is referring to "Prompt Injection as Role Confusion" ( https://role-confusion.github.io/ ). It was discussed on HN several weeks ago ( https://news.ycombinator.com/item?id=48631888 )

More ›