matchable

We differentiate between the matchable symbols and the constructors on case: lowercase means matchable, uppercase means constructor.

Patterns are now in the form x ŷ where x is a variable and ŷ is a matchable symbol.

The proper of someone is certainly more spontaneously matchable with one corpse.

This pattern has one matchable variable x̂ and one free variable constructor.

Yeah, originally GPM actually had the ability to actually upload your whole music library, matchable or not, and let you listen from the cloud.

I think you want sum types which admittedly Go doesn't have in a matchable way.

I'm not so sure the price is right, it's expensive and they are making good money on it, but I agree does have some un-matchable features such as the battery life.

This function is generic over the constructor in the sense that it matches regardless of what the constructor actually is--the constructor becomes just another matchable term.

More interesting is word boundaries: `\b` is just `\<|\>` though that should be bubbled up and usually only one side will actually produce a matchable regex.

Some structures, however, are not matchable with a regex.

I think actionable error types need to be exhaustively matchable, at least for any Rust error that you expect a machine to be handling.

If the examples are pattern matchable you can even have the agent write custom lints if your linter supports extension or even write a poor man’s linter using ast-grep.

It's not for the first taker, I'll be checking your profiles and projects and it will be for the person I consider most "matchable" with the project.

It makes sense to have an "outermost error" when you're talking about a context trace that provides information to humans, but an error which a machine responds to should be flat & statically matchable.

"Fallacies programmers believe about X" applies here: names and DOBs are far less "matchable" than you'd believe them to be.

The generally-accepted wisdom is "thiserror¹ for libraries, anyhow² for applications"—i.e., any error that's liable to be handled by a machine should be an enum of exhaustively-matchable error kinds, whereas anything that's just being propagated to the user should be stringified & decorated with context as it bubbles up.