jmillikin

14 ms·

91.
by jmillikin 2y ago
The string being discussed is: {"a": 1e2} There are no single quotes or backticks in it. Those are an artifact of posting on Hacker News.
92.
by jmillikin 2y ago
It's true for all of the parsers that I tested at the time, which covered a couple different languages (Ruby, Python, C, Haskell). It appears to still be true in at least Ruby and Python, which are probably the two most popular languag
93.
by jmillikin 2y ago
That string is a valid JSON document, and it's also a valid YAML document. The problem is that it parses to different values in those two syntaxes.
94.
by jmillikin 2y ago
What's "correct" depends on whether your YAML parser defaults to YAML 1.1 or 1.2. Most YAML parsers default to 1.1 for compatibility reasons, because if they default to 1.2 then existing YAML documents expecting 1.1 behavior
95.
by jmillikin 2y ago
I wrote a similar article two years ago, with some screenshots of people claiming YAML is a superset of JSON: https://john-millikin.com/json-is-not-a-yaml-subset It's one of those beliefs that seems like it should be
96.
by jmillikin 2y ago
Oh wow, I wasn't expecting two floppy disk copy protection articles in one week. Thanks for the correction!
97.
by jmillikin 2y ago
Previous article in the series: https://news.ycombinator.com/item?id=41346124
98.
Place expressions and value expressions in Rust(ralfj.de)
1 points by jmillikin 2y ago|0 comments
99.
Rust Dylib Rabbit Holes(davidlattimore.github.io)
63 points by jmillikin 2y ago|13 comments
100.
by jmillikin 2y ago
I've encountered the same problem with Python codebases in the LLM / machine learning space. The requirements.txt files for those projects are full of unversioned dependencies, including Git repositories at some floating ref (such
101.
Extending the #[diagnostic] tool attribute namespace(blog.weiznich.de)
3 points by jmillikin 2y ago|0 comments
102.
Interpreting decimal strings into floats (part 1)(jvernay.fr)
1 points by jmillikin 2y ago|0 comments
103.
Spider-Man (Neversoft) decompilation project progress checkpoint – July 2024(krystalgamer.github.io)
2 points by jmillikin 2y ago|0 comments
104.
by jmillikin 2y ago
As other comments have noted, the asm statement needs to have its input/output registers specified to ensure the compiler doesn't erase the "unused" values. Working example: https://john-millikin.com/unix
105.
by jmillikin 2y ago
> Languages that use the LVM — the Logical Volume Manager is a device mapper > framework that provides logical volume management for the Linux kernel — > aren’t going to have to do too much to support components because th
106.
by jmillikin 2y ago
> Am I interpreting the behavior correctly to think that: your code has > one branch per int and that branch will be predicted well when your > integers are all of similar magnitude? Yep, that's generally correct.
107.
by jmillikin 2y ago
The plot is the time to encode/decode a list of 10,000 random integers in a uniform distribution. The throughput is 2-10 GiB/s[0] on my desktop, with portable scalar operations (no SIMD). Distributions skewed toward small values a
108.
The Space Quest II Master Disk Blunder(lanceewing.github.io)
4 points by jmillikin 2y ago|0 comments
109.
A hybrid approach to semi-automated Rust verification(arxiv.org)
1 points by jmillikin 2y ago|0 comments
110.
vu128: Efficient variable-length integers(john-millikin.com)
93 points by jmillikin 2y ago|33 comments
111.
by jmillikin 2y ago
Calling WASM from VS Code has been possible for a few years: https://john-millikin.com/extending-vscode-with-webassembly The news-worthy part of the link seems to be WASI support -- instead of coding against a C-style API w
112.
A memory model for Rust code in the kernel(lwn.net)
114 points by jmillikin 3y ago|11 comments
113.
Multifaceted: The linguistic echo chambers of LLMs(blog.j11y.io)
1 points by jmillikin 3y ago|0 comments
114.
by jmillikin 3y ago
> And it's targeted in an entirely different domain -- systems programming. > Haskell is a garbage collected pure functional programming language. At the time there were many people trying to make a go of doing systems
115.
by jmillikin 3y ago
Purely my opinion: There was an era of stability in the Haskell project during which it was possible to write code for industrial purposes. A lot of people were attracted to the idea of a memory-safe language that compiled to native binarie
116.
by jmillikin 3y ago
1. About 15 years of experience in C++, 2-3 years in Rust. 2. I'm retired now, but I would have considered Rust for any greenfield project that didn't have a compelling reason to pick C++ (e.g. mandatory interop with an existing b
117.
by jmillikin 3y ago
> Does Rust make this kind of problems easy to be solved? For this specific case (specified behavior on overflow), Rust makes it trivial. All of the primitive integer types have methods such as `checked_mul()` or `saturating_add(
118.
by jmillikin 3y ago
> It's not just comparing pure WASM (bytecode) but the WASM+WASI (runtime) WASI isn't a runtime, and it's not a packaging format. It's a standard ABI for a POSIX-like syscall interface, which is useful [0] bu
119.
by jmillikin 3y ago
But they're not solving overlapping sets of problems. That's the point. * WASM competes with native machine code (x86, ARM, etc) as the format of an executable binary. * Container images compete with Apt, RPM, and tarballs as a pa
120.
by jmillikin 3y ago
> As an aside, to what degree does WASI exist _now_? It's ... rough. The impression I get (as an uninvolved third-party) is that the WASI folks set out with a goal of writing a sort of capability-based POSIX that they could

More ›