These two examples silently truncate the unmatched inputs:

```python
>>> list(map(pow, [1, 2, 3], [2, 2, 2, 2]))
[1, 4, 9]
>>> list(map(pow, [1, 2, 3, 4, 5], [2, 2, 2, 2]))
[1, 4, 9, 16]
```

The current workaround is:

```
starmap(pow, zip(vec1, vec2, strict=True))
```

Ideally, map() should support this directly.  The reasoning is the same reasoning that motivated the `strict` option for `zip()`

<!-- gh-linked-prs -->
### Linked PRs
* gh-120471
<!-- /gh-linked-prs -->

Add a "strict" option for map()
This is a GitHub Issue
repo:cpython
owner:python
Title : Add a "strict" option for map()
Issue date:

--- start body ---
These two examples silently truncate the unmatched inputs:

```python
>>> list(map(pow, [1, 2, 3], [2, 2, 2, 2]))
[1, 4, 9]
>>> list(map(pow, [1, 2, 3, 4, 5], [2, 2, 2, 2]))
[1, 4, 9, 16]
```

The current workaround is:

```
starmap(pow, zip(vec1, vec2, strict=True))
```

Ideally, map() should support this directly.  The reasoning is the same reasoning that motivated the `strict` option for `zip()`

<!-- gh-linked-prs -->
### Linked PRs
* gh-120471
<!-- /gh-linked-prs -->

--- end body ---
