VS Code. In many different cases (not only this example) Bingo omits import paths prefixes when providing quick documentation response, like if some argument was part of the package of function/method being explored, when he is not, in fact. This adds a lot of confusion when reading quick documentation. In the following example return argument must be of type func(*js.Object), not func(*Object)
saibing
commented
5 years ago
VS Code. In many different cases (not only this example) Bingo omits import paths prefixes when providing quick documentation response, like if some argument was part of the package of function/method being explored, when he is not, in fact. This adds a lot of confusion when reading quick documentation. In the following example return argument must be of type
func(*js.Object), notfunc(*Object)