{"(*FileHeader).SetModTime", Method, 0},
		{"(*FileHeader).SetMode", Method, 0},
		{"(*ReadCloser).Close", Method, 0},
		{"(*ReadCloser).Open", Method, 16},
		{"(*ReadCloser).RegisterDecompressor", Method, 6},
		{"(*Reader).Open", Method, 16},
		{"(*Reader).RegisterDecompressor", Method, 6},
		{"(*Writer).AddFS", Method, 22},
		{"(*Writer).Close", Method, 0},
		{"(*Writer).Copy", Method, 17},
		{"(*Writer).Create", Method, 0},

A657          ; valid                                  # 5.1  CYRILLIC SMALL LETTER IOTIFIED A
A658          ; mapped                 ; A659          # 5.1  CYRILLIC CAPITAL LETTER CLOSED LITTLE YUS
A659          ; valid                                  # 5.1  CYRILLIC SMALL LETTER CLOSED LITTLE YUS
A65A          ; mapped                 ; A65B          # 5.1  CYRILLIC CAPITAL LETTER BLENDED YUS

*   <IF RELEASE CONTAINS MULTIPLE FEATURES FROM SAME AREA, GROUP THEM TOGETHER>

### Bug Fixes and Other Changes

* <SIMILAR TO ABOVE SECTION, BUT FOR OTHER IMPORTANT CHANGES / BUG FIXES>
* <IF A CHANGE CLOSES A GITHUB ISSUE, IT SHOULD BE DOCUMENTED HERE>
* <NOTES SHOULD BE GROUPED PER AREA>

* `tf.data`
    * Add optional `synchronous` argument to `map`, to specify that the `map`

   "description": "Whether the container runtime should close the stdin channel after it has been opened by a single attach. When stdin is true the stdin stream will remain open across multiple attach sessions. If stdinOnce is set to true, stdin is opened on container start, is empty until the first client attaches to stdin, and then remains open and accepts data until the client disconnects, at which time stdin is closed and remains closed until the container is restarted. If this flag is false,...

}

def TF_RintOp : TF_Op<"Rint", [Pure, TF_Idempotent, TF_SameOperandsAndResultTypeResolveRef]> {
  let summary = "Returns element-wise integer closest to x.";

  let description = [{
If the result is midway between two representable values,
the even representable is chosen.
For example:

```
rint(-1.5) ==> -2.0
rint(0.5000001) ==> 1.0

                            the timeout can be set.


                            This timeout is intended to cover as close to the whole request-response transaction
                            as possible although an implementation MAY choose to start the timeout after the entire