Codeforces is a huge website with a wealth of well-defined programming problems: https://codeforces.com/help#q1
(Useful for program synthesis and other situations where you want a large problem set to play with.)
miniblog.
I don't have a favourite 'just an integer' type in Rust. I was writing a progress function for a Rust program that counts up to 20 input files.
u64 is sometimes fiddly, usize makes me think about indexing, and u32/u16/u8 make me think that something is performance sensitive.
Are there any languages that display stack traces really well? Do you have a favourite?
The trend for package managers seems to be increasingly installing packages locally, in the directory of the current project.
C: exclusively system packages
Python: system or 'virtual' (local) packages
JS, Rust: exclusively local packages
zsh is generally wonderful, and it's sufficiently like bash/POSIX sh that it works.
However, it uses 1-indexed arrays, whereas bash uses 0-indexed arrays. This totally caught me out.
It's a tragedy that ; and : are often on the same key on the keyboard, are often both legal syntax, and are so visually similar. I wonder how much programmer time has been wasted.
I'm adding R support for difftastic, and it seems to work pretty well!
> Converting to hexl format discards undo info; ok? (y or n)
I really admire how seriously Emacs looks after your undo state. Not enough software will warn you if you're about to discard undo information.
Do commas ever appear in idiomatic Clojure? It's syntactically legal but I don't think I've ever seen them in the wild.
The Indian supreme court has ruled that Google must allow third party app stores on the Google app store under antitrust laws: https://www.reuters.com/world/india/indian-startups-rejoice-android-ruling-against-google-upheld-2023-01-19/
Cases where it makes more sense to use concrete types rather than generics, even if you can be generic: https://matklad.github.io/2020/08/15/concrete-abstraction.html
Rust's RFC 3191 will let libraries package debugger scripts so you get a better experience when using gdb or windbg: https://rust-lang.github.io/rfcs/3191-debugger-visualizer.html
Defining a separate tests module so rust tests compile faster: https://matklad.github.io/2021/02/27/delete-cargo-integration-tests.html#Assorted-Tricks
What's the best keyword for function definitions?
My current hypothesis is that you want it to be short, but still pronounceable, so `fun` is the sweet spot.
I've really come to appreciate OCaml's notion of generics. It doesn't have subtyping, so e.g. you have an `int list` or an arbitrary `'a list`, but nothing inbetween.
As soon as you add constraints like Java's `List<? as Foo>` it become incredibly hard to produce good errors.
Switching between Rust and TypeScript, I really miss the Result type in TypeScript. I can kludge something with nullable types or exceptions, but it's not as nice for the caller.
The Servo browser has funding for active development again! https://servo.org/blog/2023/01/16/servo-2023/
Today I learnt about crossterm, a Rust crate for interacting with terminals in a cross-platform way: https://docs.rs/crossterm/latest/crossterm/
It handles things like is_tty() and terminal::size(), which are hard to support correctly in both Linux and Windows. I might port difftastic.
I have mixed feelings about the equality trait in Rust.
I have types where sometimes I want to compare by structure, and sometimes compare by reference.
I can only implement Eq for one, so which do I pick?
I feel like in-code docs are an underexplored design space.
Do you use comments or string literals? Before the function (e.g. JSDoc) or inside it (e.g. Python)?
Which is best? Which is the easiest to write, has the easiest tooling, or the most readable (code/HTML) artifacts?
Showing 441-460 of 7,506 posts