Josh Triplett

@jameysharp Consider inline functions, or complex constant declarations. Those may not even have symbols in the corresponding library, and may only exist in the header file.

We talked about this in today's lang meeting. This looks good, and we should merge it as soon as we stabilize the feature.

Despite `Termination` being a library trait, it's used in the language "runtime" code that runs after main, so I think it should be documented in the reference. And we should...

We discussed this again in today's @rust-lang/lang meeting, and we want to confirm that we'd be happy to have the lang/runtime aspects of this documented in the reference. (The library...

@rfcbot merge

@cramertj It looks like your concern didn't get registered; can you try again in a top-level comment?

Agreed. We're talking about a name that encompasses "value expression" and "place expression", so "expression category" seems reasonable.

r=me with an example added.

In practice, just about every crate in the ecosystem is already doing that: either using webpki-roots or rustls-native-certs or offering a choice between the two.

Ah! That makes sense. Would that also help cover cases where the certificate store needs an explicit negative entry for a CA or sub-CA, or a "must use CT" entry?