# Sema: fix in-memory coercion of functions introducing new generic parameters · gitcafe/zig

[View on GitCafe](https://git.cafe/gitcafe/zig/commit/26fdb81c16760b5aabbd1905ef96cefdf596fc3d)

Repository: [gitcafe/zig](https://git.cafe/gitcafe/zig)

Visibility: public

Requested revision: 26fdb81c16760b5aabbd1905ef96cefdf596fc3d

Requested commit: 26fdb81c16760b5aabbd1905ef96cefdf596fc3d

Commit: 26fdb81c16760b5aabbd1905ef96cefdf596fc3d

Tree: 1468581a8ea931bdc0ae4ad1ca962b682ec95901

Author: mlugg

Committer: Matthew Lugg

## Message

```
Sema: fix in-memory coercion of functions introducing new generic parameters

While it is not allowed for a function coercion to change whether a
function is generic, it *is* okay to make existing concrete parameters
of a generic function also generic, or vice versa. Either of these cases
implies that the result is a generic function, so comptime type checks
will happen when the function is ultimately called.

Resolves: #21099

```

## Parents

- [98640cbeb8a714a451821a51f3aa4ebbd488d291](https://git.cafe/gitcafe/zig/commit/98640cbeb8a714a451821a51f3aa4ebbd488d291?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zig/tree/26fdb81c16760b5aabbd1905ef96cefdf596fc3d?format=markdown)
