Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
afdbcreid
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
121.
▲
by
afdbcreid
4mo ago
Datalog is not used for borrow checking. It was used in old versions of the experimental next-gen borrow checker, Polonius. Current versions of Polonius (which is still experimental) are coded in Rust.
122.
▲
by
afdbcreid
4mo ago
I've never heard about that and I'm pretty sure it's incorrect (although "machine learning" is a wide term), do you have a source for that?
123.
▲
by
afdbcreid
4mo ago
In C/C++ the default behavior, always, is very dangerous UB. Some compilers offer an option for guaranteed wrap-around, and some compilers offer an option for controlled crash. None of them is standardized or the default. In Rust the s
124.
▲
by
afdbcreid
4mo ago
> Is there anything similar to (or better than) overleaf for collaborating on typst docs? To be clear, overleaf isn’t all that great but I sometimes work with groups that are used to it. Yes, https://typst.app/ is the of
125.
▲
by
afdbcreid
4mo ago
This doesn't matter to the post, because it is about culture, not about code. And there are plenty of ways to cause UB with modern C++ idioms.
126.
▲
by
afdbcreid
4mo ago
As for #4, you will probably be interested in https://github.com/rust-lang/crates.io/issues/326 . The crates.io team wants this, but this is complex to implement and they're understaffed.
127.
▲
by
afdbcreid
4mo ago
I've heard this from other LaTeX veterans, but as someone that has never done any LaTeX himself and was scared by all those backslashes and braces, the simple C-like syntax is a blessing.
128.
▲
by
afdbcreid
4mo ago
Rust and non-SPARK Ada are not equally safe. Ada is unsafe in the presence of data races, and also has runtime checks that slow it down, or you disable them and then it's even less safe.
129.
▲
by
afdbcreid
4mo ago
You said > I'm not convinced this is true. But it is. It is true that Rust libraries could take this position of "any API misuse causing vulnerability is a CVE" more to the extreme, currently it is applied to memory safe
130.
▲
by
afdbcreid
4mo ago
My understanding is that they claim that the average Joe writes code in a garbage-collected memory-safe language. Which is... true? but irrelevant. Such applications are not suggested to be ported to Rust. Of course, some people still do th
131.
▲
by
afdbcreid
4mo ago
What? Absolutely not. May you explain why no_std is relevant?
132.
▲
by
afdbcreid
4mo ago
You seem to have been misinformed. Rust panics on overflow in debug mode (or always if you toggle a compiler flag), and has a guaranteed wrap-around in release mode. In no case there is UB.
133.
▲
by
afdbcreid
4mo ago
> Unsafe is not necessary to trigger UB in case no_std is used I have no idea what are you talking about, no_std is just completely irrelevant here. > Nor if one of the soundness holes in the Rust programming language itself is encoun
134.
▲
by
afdbcreid
4mo ago
One possible reason: because Rust can interface with Python much more easily.
135.
▲
by
afdbcreid
4mo ago
As someone that works on rust-analyzer, complex proc macros do slow down things but complex macro_rules much more. And they're also much more complicated to understand. If you can skip `syn` or `quote` by this, for sure do it (although
136.
▲
by
afdbcreid
4mo ago
What this crate offers was RFC'd somewhat recently ( https://github.com/rust-lang/rfcs/pull/3698 , https://github.com/rust-lang/rfcs/pull/3697 ) and already available on nigh
137.
▲
by
afdbcreid
5mo ago
10x? The most generous studies I know give up to a 50% improvement.
138.
▲
by
afdbcreid
5mo ago
What operations could such frozen vector offer that std::vector does not? If there are none, it doesn't need a separate data structure.
139.
▲
by
afdbcreid
5mo ago
I wonder, if they are really only concerned about trust, will accepting external PRs but never giving commit access to external contributors work for them? Of course, if they are also concerned about the quality of external PRs then that
140.
▲
by
afdbcreid
5mo ago
They are adopting Rust ( https://ladybird.org/posts/adopting-rust/ ) and use LLMs to help with the rewrite, but not all code was migrated yet. Also it's definitely not a big-bang-rewrite-the-world-with-Claude l
141.
▲
by
afdbcreid
5mo ago
That's not source-available, that's still open-source. Quoting Wikipedia: > Source-available software is software released through a source code distribution model that includes arrangements where the source can be viewed, and
142.
▲
BorrowSanitizer: Find Rust aliasing violations even with FFI
(github.com)
1 points
by
afdbcreid
5mo ago
|
0 comments
143.
▲
by
afdbcreid
5mo ago
This is not true. Well, it kinda is, but nobody will be stupid enough to hand-code an account recovery where you get to type any email address. The reason it worked there is that the designers of the system didn't anticipate that the A
144.
▲
by
afdbcreid
5mo ago
It's true that panics (unlike UB) cannot automatically time-travel, but your justification is weak. Recovering from panics can only prevent this optimization if the loop have side effects, and LLVM knows when panic=abort is set.
145.
▲
by
afdbcreid
5mo ago
Julia is not a systems language. Also its design (GC, dynamic typing) does not allow it to reach exactly the same level as C++.
146.
▲
by
afdbcreid
5mo ago
How can you create constant-time code with Nim when none of its backends support it (e.g. LLVM may turn an apparently-constant-time code into non-constant-time assembly)?
147.
▲
by
afdbcreid
5mo ago
So? How is that an argument that C++ is more performant than C? It's only an argument that it's not less performant.
148.
▲
by
afdbcreid
5mo ago
I explicitly acknowledged that: > The only candidate is using virtualization and void* pointers instead of monomorphized generics which some C code does for the lack of better options, but that's not a problem in Rust as well. But i
149.
▲
by
afdbcreid
5mo ago
Is C++ more performant than C? I find this hard to believe. C++ does not have any construct that cannot be replicated, or is not common, in C. The only candidate is using virtualization and void* pointers instead of monomorphized generics w
150.
▲
by
afdbcreid
5mo ago
The overhead of bounds checking varies a lot. In the common case it's negligible (few percents), but in some cases, depending on what you build, it can go up to even 20%. And if it prevents autovectorization it can cost even more. Ther
More ›