Viewing profile — ycitm

The next sentence in the quote hasn't aged so well - "What weather they shall have is not ours to rule."

Most importantly, this means my type system N-queens solution now works for an 8x8 chessboard (actually up to 10x10) instead of complaining about recursion depth: https://www.richa…

Doesn't seem to be any discernable improvement on the Zoom Cat Lawyer.

You can also play around with the code in the TypeScript playground: https://www.typescriptlang.org/play?#code/PTAEEkDsAsEMBsCmAa...

Ah, thank you so much! Great spot. I've corrected this, and credited you in the errata - https://www.richard-towers.com/2023/03/11/typescripting-the-...

I don't think there's any way to do iteration in the type system (other than recursion), so there's no way around it. I considered forking the compiler to set a deeper limit, but a…

I wondered if anyone would spot this :) There's a recursion depth limit of 500 on the TypeScript compiler, which prevents this solution working for N > 7 Even Aphyr's original Hask…

The series is actually by Aphyr: https://aphyr.com/tags/interviews This post is a pastiche of https://aphyr.com/posts/342-typing-the-technical-interview

The runes are mostly "just because", but there is a reason. Ideally, I would have written: type Nil = unique symbol Which would ensure the Nil type wouldn't match with anything but…

If you've got any experience or interest in programming, I'd recommend having a stab at Google Summer of Code[0]. [0] - https://developers.google.com/open-source/gsoc/

One of my new years resolutions was to learn to type faster. To get some practice I started taking notes in all the meetings I attend. This wasn't common practice in my team before…

If you have control of your nameservers you can use cloudflare's free TLS offering and keep your current webhost.

Surround support was just added in IdeaVim 0.46. From the release notes: Support for vim-surround commands ys, cs, ds, S, enable it with set surround in your ~/.ideavimrc

Looks like it's just an optimization. If you change to let test_curry x y = x + y + x You get the expected output function f(param) { return test_curry(32, param); }

You could call your js function with a string, and rather than a compile time error you'd get broken behaviour at runtime.

At least in new versions of Chrome, NodeList is iterable, so you can use forEach and map on it. https://medium.com/@devlucky/nodelist-object-is-finally-an-i...

Some nice intuitive stuff in the help, too. :help paragraph [...] The default is "IPLPPPQPP TPHPLIPpLpItpplpipbp" [...] (they're nroff macros, but pretty baffling to a beginner)

Perhaps Tōkaidō Shinkansen would be a better example? 331 trains / day, 391 thousand passengers / day according to: http://english.jr-central.co.jp/company/ir/annualreport/_pdf... …