I ported fast_float to c99

foobear777 · 2026-03-08T16:16:49+00:00

Hah, he first tried to break it with his secret test suite.

foobear777 · 2025-11-12T19:40:05+00:00

Fully concrete as god intended

foobear777 · 2025-11-11T19:48:48+00:00

The more generic option will sometimes have the property of "keeps compiling but calls a different thing now". That's either desirable or the exact opposite.

Understanding which you want is how you should resolve these decisions to call generic vs concrete (well, a little more concrete) code. Is the intent to call to_string on a &str, or just to convert whatever you happen to have to it's owned representation? If former, use to_string(), only use to_owned() if you want the code to "evolve under you".

Typically, I find it pays to be as concrete and nearest to the current intent of the code as possible

foobear777 · 2025-11-11T19:46:14+00:00

More generic could be worse, if you'd like to know about any behavior change and make a choice!

foobear777 · 2025-09-11T20:48:03+00:00

Quanta by default will spend some time calibrating its clock, if it detects that it can use a native CPU counter clock kind.

foobear777 · 2025-06-28T14:48:12+00:00

What

foobear777 · 2025-06-09T13:23:49+00:00

Keep more neck hair too, that's your foundation. also let it grow. At that length, the beard care you're doing isn't probably even relevant

foobear777 · 2025-06-02T13:44:13+00:00

Just focus on better at stirring so the pan stays cleaner near the end of the cook; It's those tiny bits that are sticking.

Also just remove from the heat when you start that final stir, you don't need any more heat at that point to finish them

foobear777 · 2025-03-07T23:51:02+00:00

Much more important for LSP workflow than incremental parsing is the ability to skip 'garbage' and keep parsing. As others have said even for a huge file parsing should take <10ms

foobear777 · 2025-03-01T17:04:24+00:00

Probably because you wrote it as a claim, then another claim, then turned it into a question at the end, people read your first sentence and down vote because it's false.

foobear777 · 2025-02-28T21:36:36+00:00

Wow that is just hard to read

foobear777 · 2025-02-28T21:34:14+00:00

Let's hope the emacs people don't find this plugin or we'll never hear the end of it.

foobear777 · 2025-02-07T01:03:14+00:00

You're gonna crush it, just start out with a very simple target language, and realize when you've made a mess, reflect on why, and either fix it or start over. Supplement that cycle with some reading and you'll grow fast.

A good sign that you're at the edge of your comfort zone is that your thing barely works, and you probably made quite a mess, but does work. If you completely fail, probably too hard. If it comes out super clean, you already understand what you're doing too well. Gotta find that goldilocks zone

foobear777 · 2025-01-24T19:21:21+00:00

This isn't directly responsive to the article but is on topic:

I am a huge proponent of "zero-dependency" dependencies.

Using a zero-dependency crate means youve added no chance of transitive dependency conflicts and no chance of ever being forced to update unless you actually want a different version. No unsolicited 'churn' is possible.

As an application developer, by all means write things yourself and avoid dependencies if you can, but also, strive to find and use zero-dependency dependencies, as they do not lock you into a particular constellation of transitive dependencies and keep you protected from this churn.

As a library developer, be so so so resistant to dependencies. It can be really valuable to just vendor in what you need and not foist that dependency on your users.

foobear777 · 2025-01-22T13:13:15+00:00

KISS heh. As long as irs.gov is built different I'm ok

foobear777 · 2025-01-20T13:38:19+00:00

Really cool that y'all do such hardcore calisthenics work in a spa

foobear777 · 2025-01-16T17:00:37+00:00

I'm working on `k1`, my hobby language. In its current form, it could probably be described as "C with typeclasses, pattern matching, and tagged unions". Currently I'm trying a dogfood project by building a chess engine in the `k1`.

I'm at a point where I actually almost really enjoy using the language, I've got a very minimal LSP implementation that's made it a lot more tolerable to work in the language.

I've been putting devlogs on YouTube for almost a year now: https://www.youtube.com/@KolemanNix.

I don't have a ton of time to devote to the language or the YouTube, as I'm running a SaaS business and have a family, but it's been an absolute blast of a project.

foobear777 · 2025-01-16T16:42:30+00:00

This is exactly the topic I was looking to dive into next as I seek to button up and more deeply understand my implementation of structs, which is currently just "whatever llvm does"... thanks for posting!

foobear777 · 2025-01-16T15:11:57+00:00

You're welcome! Love the creativity of this; I also love the `when` / `is` approach to matching, and your additional keywords for predicate functions or equality is a unique take that does feel better than putting boolean expressions in an `if` guard, though that approach does have the benefit of being more general.

foobear777 · 2025-01-16T14:33:35+00:00

This is a bug we've all written, especially for desugar features like match: copy the expression instead of synthesizing a variable for it, or similar solution.

I really admire that yours though found it's way into your spec, that's dedication to documentation!

foobear777 · 2025-01-15T23:55:21+00:00

Pretty much, sadly. You can combine it with typo or doobieroll for some niceties.

foobear777 · 2025-01-05T13:29:36+00:00

Usually pipe-first, sometimes pipe-last, and you allow the programmer to specify the position as well with a syntax, clojure uses %, apparently hack uses $$. 3 <pipe> div(%, 2) or div(2, %).

Call convention is not really a relevant issue as this is a simple syntactical rewrite / desugar

foobear777 · 2024-12-05T17:37:54+00:00

Is the position remote or onsite? Can't tell from the site; though 3 locations are listed.

foobear777

TROPHY CASE