mswphd

10 ms·

151.
by mswphd 4mo ago
"people with disabilities that make it impossible for them to succeed in normal school" is not a clearly divisible population from the regular student population though. Many (but not all) districts deal with disabilities via IEPs
152.
by mswphd 4mo ago
Many boardgames are also available in spanish. BoardGameGeek is a popular boardgame website. Unfortunately, they don't seem to have an ergonomic way to filter searches on a spanish-language version of the game being available. But you
153.
by mswphd 4mo ago
hard to give recommendations without more information. For example 1. what languages does he know? there are boardgames that are localized into other languages. Probably the easiest route tbh. 2. what kinds of games does he like? for exampl
154.
by mswphd 4mo ago
for context: in rust the "translation unit" is a crate (in C++, each source file is its own translation unit). So you only get parallelism across crates when compiling in rust. When you have a single-crate project, this means that
155.
by mswphd 5mo ago
if you have an OOM and want to log why, if your logging allocates it will likely fail as well. You could in principle work around this with enough effort, but "properly" handling OOM is typically much more trouble than its worth.
156.
by mswphd 5mo ago
There's a number of things about rust that help compared to other statically typed languages. 1. the compiler gives very high quality error messages. It helps humans, and also helps LLMs 2. Rust reduces memory management to local reaso
157.
by mswphd 5mo ago
a few things 1. thiserror just does codegen of the "standard" enum things people do. if you find debugging thiserror difficult, just write out the enums manually. sure it's uglier, but (roughly) equivalent. so its preferable
158.
by mswphd 5mo ago
also thiserror isn't incompatible with io::Error? all thiserror does is do code generation for "typical" enum errors. The errors it generates are normal rust code though, and the fact that they're generated by thiserror
159.
by mswphd 5mo ago
circular breathing is useful for other instruments as well, though it's not typically a technique that's necessary until you get to fairly high levels.
160.
by mswphd 5mo ago
there is the other (significant) issue, that wealth (and its many benefits) are inherited, and by all indications the exponential advantage seems to pass down through generations (at least recently).
161.
by mswphd 5mo ago
we used to ship mass lists of addresses and phone numbers to people in each town and it was fine/appreciated.
162.
by mswphd 5mo ago
isn't the whole point of C that it's portable assembly though? needing to understand the target platform/compiler's behavior to write correct code seems to cut against that claim quite a bit.
163.
by mswphd 5mo ago
Crystals are a form of solid that in some sense have "long range regularity". One way (the obvious way) to have this is to have a (translational) symmetry. For a while, it was thought this was the only way. Aperiodicity (in the se
164.
by mswphd 5mo ago
Another example: For years rust was limited on performance optimizations in LLVM. Specifically, it was difficult to get LLVM to properly optimize for Rust's generated code, namely where one can make strong aliasing (and non-aliasing) s
165.
by mswphd 5mo ago
it is, but it's a little confusing here because the library/consumer of the library are the same person. This is a bug in the library, namely in Bun's PathString implementation. The bug is a soundness issue, precisely because
166.
by mswphd 5mo ago
`unsafe` isn't viral. I can write fn safe_function(...) -> (...) { // do unsafe things here } then `safe_function` can be called from safe code, and still trigger UB. This wouldn't be a soundness issue in th
167.
by mswphd 5mo ago
Lifetimes would prevent the particular use-after-free example here, but the UB that miri currently flags would still exist, as it's related to pointer provenance, not lifetimes. https://www.reddit.com/r/rust/c
168.
by mswphd 5mo ago
even when you can review the code, it's good to have the compiler check for you. This is for similar reasons why it's better to have CI check correctness on each code change, vs testing the code thoroughly one time, and then being
169.
by mswphd 5mo ago
This already happens all the time in rust, including in the standard library. The typical pattern is to define your CheckedType to be pub struct CheckedType(UncheckedType); e.g. where its inner field is private. Then, you only present safe
170.
by mswphd 5mo ago
CSrankings.org is a (flawed for sure, but still) ranking of the research output of various graduate institutions. China has 3 of the top 10 ranked universities according to this ranking. https://csrankings.org/#/index?a
171.
by mswphd 5mo ago
it was illegal for private schools to have grad student unions until ~2016, as (private) graduate students were not classified as employees. https://www.aaup.org/brief/columbia-university-364-nlrb-no-9...
172.
by mswphd 5mo ago
it is using the agent SDK, see https://github.com/agentclientprotocol/claude-agent-acp/blob...
173.
by mswphd 5mo ago
worth clarifying the build parallelism is because the fundamental unit of compilation in rust is the crate. so the main option available to cut down the running time of a large crate is to split it into smaller crates.
174.
by mswphd 5mo ago
I've seen this floated as a response to the current anxieties over LLMs in math. Namely in applied math, LLMs being good at pure math may actually allow the import of pure math techniques. Unclear if that will pan out, but it's in
175.
by mswphd 5mo ago
You can read some motivation for it at the following link https://rust-lang.github.io/rust-project-goals/2024h2/Rust-f... note that it also discusses `std::offload`, which might also be of interest.
176.
by mswphd 5mo ago
there is a strong anti-QKD bias among experts who understand QKD. It is fun academic concept, but does not solve a real world problem, and does not use techniques available at remotely comparable costs to classical cryptography in the real
177.
by mswphd 5mo ago
BB84 (and QKD overall) requires authenticated channels. You have to get those somewhere. You can get them from an information-theoretically secure MAC, but it has significant downsides. You can get them with computationally secure primitive
178.
by mswphd 5mo ago
you cannot be mathematically rigorous with computational lower bounds. It is not possible with current mathematics. No ones that are relevant to cryptography exist, so any computational cryptography must separate into 1. provable constructi
179.
by mswphd 5mo ago
that's not what people say? and pre-quantum crypto is also vulnerable to yet discovered classical algorithms?
180.
by mswphd 5mo ago
I wouldn't call it "solid theoretical footing". The rough sketch of QKD is 1. BB84 key exchange requires an authenticated channel. typically you do this with a 2. Carter-Wegman MAC, which is information-theoretically secure,

More ›