trws

6 ms·

1.
by trws 6mo ago
Everything else in the siblings is true, but remember that the language and std types in rust all do this already. Most of the time it’s better to use a native enum or optional/result because they do this in the compiler/lib. It’s
2.
by trws 6mo ago
It’s Hana Dusikova’s paper IIRC.
3.
by trws 6mo ago
There’s a paper in flight to add a stdlib type to handle pointer tagging as well while preserving pointer provenance and so-forth. It’s currently best to use the intptr types, but the goal is to make it so that an implementation can provide
4.
by trws 10mo ago
I worked @fzakaria on developing that idea. It actually worked surprisingly well. The benefits are mostly in the ability to analyze the binary afterward though rather than any measurable benefit in load time or anything like that though. I
5.
by trws 1y ago
I liked the article. I saw your PS that we added it to the working draft for c++26, we also made it part of OpenMP as of 5.0 I think. It’s sometimes a hardware atomic like on arm, but what made the case was that it’s common to implement it
6.
by trws 1y ago
Quite so. We would have too, but I left out the nasty bit that someone had at one point put a callback argument in an internal launching API that runs between fork and exec. Still working on squashing the last of those.
7.
by trws 1y ago
The other place it comes up is launchers and resource managers. We actually have a series of old issues and implementation work on flux (large scale resource manager for clusters) working around fork becoming a significant bottleneck in par
8.
by trws 1y ago
I largely agree, and use these patterns in C, but you’re neglecting the usual approach of having a default or stub implementation in the base for classic OOP. There’s also the option of using interfaces in more modern OOP or concept-style l
9.
by trws 1y ago
You have this largely right, but I need to defend the Radeon driver a bit here. The driver that caused all the problems was the proprietary fglrx driver, not the open source Radeon driver. The issue with the Radeon driver wasn’t stability,
10.
by trws 1y ago
I just started giving it a try again about a week ago, and I second this. A year ago it was nearly unusable for any extension outside their preferred list, now it’s largely a pleasant experience.
11.
by trws 1y ago
I’m rather hoping there’s something better, but various CAD formats support specifying assemblies of objects, and joints between those objects that can represent properties like that. Often this comes with at least some level of simulation,
12.
by trws 1y ago
The short answer is yes, Linux can be informed to some extent but often you still want a memory balloon driver so that the host can “allocate” memory out of the VM so the host OS can reclaim that memory. It’s not entirely trivial but the to
13.
by trws 1y ago
> Is this obvious, simple, and default behaviour? Yes. There are two options IIRC, minimum layers and maximum layers (one per dep by default unless that makes too many, which is handled automatically) depending on what you want, and it’s
14.
by trws 1y ago
Much as the article makes good points, I find it difficult to believe that the list of meats banned by kosher and halal matches the top allergies and disease risk factors as well as it does without some intent. Pork was, until very recently
15.
by trws 2y ago
The first one that comes to mind is something I haven’t done lately but used to do constantly , enough so that I wrote a custom fuse filesystem to combine isofuse with http handling, and that’s parsing an index from something with a range
16.
by trws 2y ago
An inotify replacement that can work at whole FS level (and doesn’t require root/admin like the existing option) would be amazing. To be honest, I don’t see a reason it would be hard at the whole filesystem or perhaps mount level unles
17.
by trws 2y ago
CI is the big one, or similar testing against older versions for backwards compatibility. Usually good enough to just compile for it on MacOS, but sometimes we get a surprise in a third party library or something that only shows up on an ol
18.
by trws 2y ago
A small refinement here, your statements are largely my experience dealing with people linking against gpl3 software because of the vitality and the patent exemptions. Most places run gpl3 stuff just fine. The one organizations won’t to
19.
by trws 2y ago
I think your comment was once completely correct, but there is now also a “cpuset” cgroup in addition to the classic cpu setting. The cpuset control gives something equivalent to sched_setaffinity but stronger since the client processes can
20.
by trws 2y ago
Some computation tasks can tolerate the latency if they’re written with enough overlap and can keep enough of the data resident, but they usually need more performant networking than this. See older efforts like rcuda for remote cuda over i
21.
by trws 2y ago
If I had to guess, I’d say submodules. I work on a couple of projects with no submodules and find work trees great for those, but incredibly painful for the projects that have them. This seems to be getting better in newer git versions, but
22.
by trws 2y ago
I fell very far down this rabbit hole trying to figure out the history of library link orders and symbol resolution. One fun outcome of which was finding that the first ever public release of a manpage for ld.so on Linux listed RPATH as dep
23.
by trws 2y ago
It depends on your needs. I haven’t used that stack, but I maintain projects that have to use autotools, cmake and about a dozen different compilers together to build, 3 of them Fortran compilers. Bazel is easy if you have exactly one bless
24.
by trws 2y ago
I’ve run into both. I sit between a research organization and a production organization and have to produce artifacts on both sides, this suits me quite well because I’m very much an applied research person. If it’s not feasible or tangible
25.
by trws 2y ago
That’s correct AFAIK, but assumes a specific kind of JIT. It’s entirely possible for a JIT compiler to produce shared libraries (dyld files in this case) which are then loaded into the process with dlopen. It’s slower to produce a compiled
26.
by trws 2y ago
I’m a bit perplexed how you mean. Mkdir is a thin wrapper around `mkdir(const char*pathname, int mode)` from libc, or at least was before things like -p were added. Everything else is handling arguments and various failure modes. Famously &
27.
by trws 2y ago
Yes. That’s the point. Edit: that’s too glib. The restrictions currently aren’t technical, they’re enforced by what is and isn’t allowed in the App Store. It’s perfectly possible to build the software on iOS today, you just can’t distribute
28.
by trws 2y ago
This is all technically true, but an IDE that cannot compile and run the code on the local device is missing something. The prohibition on JIT or otherwise compiling on device and running the result is a big blocker for a lot of true native
29.
by trws 2y ago
They do need to rework their development processes. It’s worth noting though that there are two (kinda three) different drivers with very different quality and different teams behind them. There’s the binary driver, on windows and the fglrx
30.
by trws 3y ago
I’m sincerely curious. While I realize that using dwarf for unwinding is annoying, why is it so bad that it’s worth pessimizing all code on the system? It’s slow on Debian derivatives because they package only the slow unwinding path for pe

More ›