Allow defer statements after error checking

[cloudlena]

It is good practice to defer a close statement for a HTTP response body after the error check as discussed in https://stackoverflow.com/questions/33238518/what-could-happen-if-i-dont-close-response-body-in-golang#33238755

In my opinion, this defer statement should logically be part of the block where the body originates so I think we should allow the following:

resp, err := client.Do(req)
if err != nil {
    return err
}
defer resp.Body.Close()

instead of enforcing the following:

resp, err := client.Do(req)
if err != nil {
    return err
}

defer resp.Body.Close()

[bombsimon]

Hi, thanks for the report!

Seems reasonable, I'll add this to the TODO list!

[DmitriiDunaev]

It might be beneficial to allow methods other than Close() to be used in defer. Many libraries use names like Free(), Release(), Shutdown(), etc.

[bombsimon]

It might be beneficial to allow methods other than Close() to be used in defer. Many libraries use names like Free(), Release(), Shutdown(), etc.

This was reworked in #133 in June, it's now allowed to defer any call as long as it's used two statements above. There are a bunch of examples with allowed values in the test:

wsl/testdata/src/default_config/defer.go

Lines 6 to 35 in 7edb3ef

	undoMaxProcs, err := maxprocsSet()
	if err != nil {
	return fmt.Errorf("failed to set GOMAXPROCS, err: %w", err)
	}
	defer undoMaxProcs()
	callback, x := getCb()
	if x != b {
	return
	}
	defer callback()
	resp, err := client.Do(req)
	if err != nil {
	return err
	}
	defer resp.Body.Close()
	db, err := OpenDB()
	requireNoError(t, err)
	defer db.Close()
	tx := BeginTx(db)
	defer func() {
	EndTx(tx, err)
	}()
	thingOne := getOne()
	thingTwo := getTwo()
	defer thingOne.Close()