pSpaces/goSpace: space/tuplespace.go; 4 LoC

Found a possible issue in [pSpaces/goSpace](https://www.github.com/pSpaces/goSpace) at [space/tuplespace.go](https://github.com/pSpaces/goSpace/blob/d2861cf774949c04ce1acdb14d9c7d51f0391735/space/tuplespace.go#L627-L630)

Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.

> function call at line 628 may store a reference to t

[Click here to see the code in its original context.](https://github.com/pSpaces/goSpace/blob/d2861cf774949c04ce1acdb14d9c7d51f0391735/space/tuplespace.go#L627-L630)

Click here to show the 4 line(s) of Go which triggered the analyzer.

```go
for _, t := range tupleList {
defer funcDecode(fr, &t)
funcEncode(fr, &t)
}

```

Click here to show extra information the analyzer produced.

```
The following graphviz dot graph describes paths through the callgraph that could lead to a function which writes a pointer argument:
digraph G {
"(funcDecode, 2)" -> {}
}

No path was found through the callgraph that could lead to a function which passes a pointer to third-party code.

```

Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.

commit ID: d2861cf774949c04ce1acdb14d9c7d51f0391735

Start with space/tuplespace.go lines 627-630 at commit d2861cf774949c04ce1acdb14d9c7d51f0391735. Inspect how funcDecode and funcEncode use &t, especially the deferred call, then classify the finding as a Bug, Mitigated, or Desirable Behavior based on the analyzer's report.

Written by the indexing model from the issue text.