Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ojeda
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
3 ms
·
1.
▲
by
ojeda
6mo ago
I like Visual Studio, and have used it for C++. And, yes, it would be great if they add native support for Rust. But that would not make me pick C++ over Rust. Other requirements may.
2.
▲
by
ojeda
6mo ago
My reply was about Win32 and typical C++ development. Obviously other projects may be best written in C# or other languages and frameworks. Anyway, Microsoft is the one providing the Rust crate(s) I linked, and according to the releases it
3.
▲
by
ojeda
6mo ago
Yeah, Win32 (Windows API) will be around for a long time one way or the other, and there is a ton of tooling and docs around it. Even for non-Windows usage it is to be considered in certain situations. > Don't be swayed by the propa
4.
▲
by
ojeda
6mo ago
> which indicates the undefined behavior actually helps rather than hurts when used with good tooling No, one doesn't need undefined behavior for that at all (which does hurt). What actually helps is diagnosing the issue, just like
5.
▲
by
ojeda
2y ago
> The Rust Project says R4L is a “flagship” goal Rust's 2024H2 and 2025H1 flagship goals are about getting Rust for Linux into stable Rust, implementing features we need and so on. We really appreciate being a flagship goal of their
6.
▲
by
ojeda
4y ago
N2834 ("Deprecate the %n format specifier in C2X") was discussed in WG14 (no consensus). https://www.open-std.org/jtc1/sc22/wg14/www/docs/n2834.htm
7.
▲
by
ojeda
5y ago
"Interface files" that are intended as a form of documentation should be generated automatically instead. As for interface vs. implementation docs, nothing precludes having both in a single file either.
8.
▲
by
ojeda
5y ago
C++ may get pattern matching with P1371, which may make visiting look more reasonable: std::string_view print_type(const variant_type& jtt) { using namespace std::literals; return inpect (jtt) { <dou
9.
▲
by
ojeda
5y ago
For C, there is a paper (pending publication) about this. No promises, of course, but the committee will at least have a look.
10.
▲
by
ojeda
5y ago
> Zig and Rust are safe languages Zig is a nice improvement over C, but it is not safe. There is work in progress ( https://github.com/ziglang/zig/issues/2301 ), but from what I can tell, key details are sti
11.
▲
by
ojeda
5y ago
To be fair, I was just a teenager back then and I was out of kernel development for quite a few years afterwards. But you are right, this is not coming from the Rust community itself. In fact, several independent groups have been thinking o
12.
▲
by
ojeda
5y ago
> I'm not the first one lamenting the lack of experimentation in CS. See ... Take your first IEEE paper's abstract: "Empirical software engineering research needs research guidelines to improve the research and reporting p
13.
▲
by
ojeda
5y ago
> the almost complete lack of empiricism in Computer Science Claiming that an entire science field "lacks empiricism" is quite brave, and definitely false in the case of CS. Perhaps you are talking about software engineering in