The spacing between the lines in the credits screen does not match the official D2 client. The spacing needs to be adjusted to accurately match what the original client does.

In code_translator.rs, @bnjbvr noted (bytecodealliance/cranelift#1104 (comment)) that the boolean logical operator CLIF is identical between the scalar code and the SIMD code; e.g., let (a, b) = state.pop2(); state.push1(builder.ins().bor(a, b));. This code duplication can be removed by merging the match of some SIMD and scalar operators (the logical ones for su

Steps to reproduce

• futures-preview = { version = "0.3.0-alpha.19", features = [ "async-await" ] } in Cargo.toml as recommended in §3.1.
• Try to build the example in https://book.async.rs/tutorial/sending_messages.html

use futures::channel::mpsc; // 1
use futures::sink::SinkExt;
use std::sync::Arc;

type Sender<T> = mpsc::UnboundedSender<T>; // 2
type Receiver<T> = 

As requested in #2626, we should document all the fields available via the context as they are not really discoverable. The doc should include grpc functions like SetHeader/Method/etc as well as fields stored directly within the context like metadata and peer info.

• I've read, understood, and done my best to follow the *CONTRIBUTING guidelines.

I was searching what was the best way to log Alamofire requests and responses and the first thing I found was [How can I log each request/response using Alamofire?](https://stackoverflow.com/questions/26736428/how-can-i-log-each-request-resp

Package version eg. v8, v9:

v9

Issue, Question or Enhancement:

Is it possible to use oneof validation with values containing space character? Tried with single quote but it did not seem to work.

Code sample, to showcase or reproduce:

type Data struct {
    Status string `json:"status" validate:"required,oneof='Awaiting Verification' 'Verified' 'Failed Veri

Add some docs for the new metrics added in #7257.