Fix crash on direct inference via nodes.FunctionDef._infer

[DanielNoord]

Steps

• For new features or bug fixes, add a ChangeLog entry describing what your PR does.
• Write a good description on what the PR does.

Description

Fix as suggested in the issue.

Type of Changes

	Type
✓	🐛 Bug fix

Related Issue

Closes #817

[Pierre-Sassoulas]

Shouldn't this be in 2.11.1 ?

[DanielNoord]

I saw no direct reason to cherrypick as pylint doesn't depend on it and the issue hasn't gained a lot of traction in the last year, but if @eugene57 is eagerly waiting for it we can definitely include it in 2.11.1

[Pierre-Sassoulas]

I was thinking crashes and bugs should be backported. But it's true that it increase the maintenance burden. Maybe only crashes ?

[DanielNoord]

I was thinking crashes and bugs should be backported. But it's true that it increase the maintenance burden. Maybe only crashes ?

Then we would need to back port this as this prevents an IndexError 😅

I think not releasing a hotfix if nobody really depends on it asap is fine. We have normal releases for "cold fixes" 😄

[Pierre-Sassoulas]

Let's try to make a two bug fix release for 2.11.1 and see how much time it takes :)

[Pierre-Sassoulas]

I can't suggest the change in interface for the changelog 2.11.1 is outside the diff. The rest LGTM.

[DanielNoord]

@Pierre-Sassoulas Do you know you can use . on the Github website to launch a web-version of VS Code to make simple changes like those? Since you're maintainer of the repo you have write access to my branches.

[Pierre-Sassoulas]

Wow, this is actually impressive (and a little slow too, but less than doing adding a remote and modifying locally). Thanks for the tip !

[DanielNoord]

@Pierre-Sassoulas Yeah I never used it much, but found out recently how useful it is for small changes to a PR