notriddle

Crater results for math-core

https://gist.github.com/notriddle/108fe255ffa9f490ed8ade262935eb53

Flanking rules in GitHub to compare with pulldown-cmark and commonmark-hs

jgm might want to change some of these to make pandoc's "gfm" mode match GitHub more closely.

left$\sqrt{2}$right

notriddle

clippy 0.1.88 (9f74df2b61 2025-04-29)

### Reports

target/lintcheck/sources/anyhow-1.0.86/src/backtrace.rs:27:27 clippy::incompatible_msrv "current MSRV (Minimum Supported Rust Version) is `1.39.0` but this item is stable since `1.65.0`"
target/lintcheck/sources/anyhow-1.0.86/src/backtrace.rs:27:27 clippy::incompatible_msrv "current MSRV (Minimum Supported Rust Version) is `1.39.0` but this item is stable since `1.65.0`"
target/lintcheck/sources/anyhow-1.0.86/src/backtrace.rs:27:27 clippy::incompatible_msrv "current MSRV (Minimum Supported Rust Version) is `1.39.0` but this item is stable since `1.65.0`"
target/lintcheck/sources/anyhow-1.0.86/src/backtrace.rs:27:27 clippy::incompatible_msrv "current MSRV (Minimum Supported Rust Version) is `1.39.0` but this item is stable since `1.65.0`"
target/lintcheck/sources/anyhow-1.0.86/src/backtrace.rs:27:27 clippy::incompatible_msrv "current MSRV (Minimum Supported Rust Version) is `1.39.0` but this item is stable since `1.65.0`"
target/lintcheck/sources/anyhow-1.0.8

notriddle

The biggest mistake is treating Postel's Law as a suggestion. It's a law, just like Moore's Law, Hyrum's Law, Goodhart's Law, and the Law of Diminishing Returns.

In an ecosystem of interoperating implementations, accepting sloppy input and emitting strict output is the locally-optimal strategy to avoid your implementation being seen as the direct cause of problems. This is contingent on two "facts":

• The upside to accepting sloppy input is immediate, while the downside is far away and diffuse.
• Accepting sloppy input is a one-way ratchet. It's easy to add, sometimes, if it happens to be easy to do it with your current implementation strategy. But, once people start relying on it, it's very painful to remove.

This is a collective action problem, because, in an ecosystem where every other implementation is strict on both emitting and consuming input, the locally-optimal strategy is still Postel's Law, as long as bugs that are easy to work around exist. Advising individual development teams that "Postel

notriddle

// need to escape specials
// https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Regular_expressions
const REGEX_SPECIALS = /[\$\(\)\*\+\.\/\?\[\\\]\^\{\|\}]/;
class EditDistanceCalculator {
	constructor(string, limit) {
		this.string = string;
		this.current = [];
		this.prev = [];
		this.prevPrev = [];
		this.matcherRegExp = new RegExp("^" + this.buildMatcherRegExp(string, limit) + "$");

notriddle

Introduction

Note: this is not a policy doc. At least, not yet.

This is a pile of notes that should probably be integrated into the rustc-dev-guide at some point. These roles, at least for me, inform where and how I've designed features and pages in rustdoc.

With these roles written down, I'm going to try to avoid referring to a "rustdoc user" most of the time, because that's not usually specific enough. Rustdoc has three interfaces, with three different audiences, who, sometimes, overlap.

notriddle

My [cmark-gfm][^c].

My [cmark-gfm][cmark-gfm][^c].

My [cmark-gfm][][^c].

My [cmark-gfm] [^c].

My [cmark-gfm[^c]].

notriddle

Songs that simply loop are a popular way to annoy people. ¹

• I know a song that gets on everybody's nerves
• Ninety-nine bottles of beer on the wall

Songs that simply loop are a popular way to annoy people. ²

Footnotes

1. • The song that never ends
   ↩
2. • The song that never ends 2
   ↩

notriddle

Footnotes ¹ [^many].

Footnotes

1. first paragraph inside footnote ↩

notriddle

#!/bin/bash

print-usage-and-die() {
	echo "Usage: diffpkg.bash [cargo|npm] [pkg1] [pkg2]"
	echo "       pkg1 and pkg2 can have formats NAME-VERS, NAME@VERS, NAME:VERS, or NAME=VERS"
	exit 1
}

extract-name() {
	case "$1" in

notriddle

By "rustdoc", I mean the API documentation webapp used by Rust. The Book is rendered using a different application, called mdBook, and only some of this advice is really applicable to it.

I hope you take my copycat txties as the compliment that I intend, by the way.

Step 1: get the rust toolchain

The first step is to get the Rust code. To help compare the old version with the new one, I set up a separate worktree for the new version, and keep the old version around. It's a lot like cloning the repository twice, but it doesn't require two downloads.

user=notriddle

cd ~/Development