On Thursday, February 16, 2017 at 9:11:08 PM UTC+1, Ian Lance Taylor wrote:
> identified one approach using finalizers. That approach will work
> today as Go's garbage collector never moves items.
>
Thanks Ian for your help. FWIW, I just have coded this objvalmo.go file and
function
On Wed, Feb 15, 2017 at 9:42 PM, Basile Starynkevitch
wrote:
>
> On Wednesday, February 15, 2017 at 9:01:58 PM UTC+1, Tamás Gulácsi wrote:
>
>>
>> Why do you need this?
>> You want the GC do the housekeeping for you, but I'm sure you won't be
>> happy with the result, as
On Thursday, February 16, 2017 at 6:42:05 AM UTC+1, Basile Starynkevitch
wrote:
>
>
>
> On Wednesday, February 15, 2017 at 9:01:58 PM UTC+1, Tamás Gulácsi wrote:
>
>
>> Why do you need this?
>> You want the GC do the housekeeping for you, but I'm sure you won't be
>> happy with the result,
On Wednesday, February 15, 2017 at 9:01:58 PM UTC+1, Tamás Gulácsi wrote:
> Why do you need this?
> You want the GC do the housekeeping for you, but I'm sure you won't be
> happy with the result, as the GC's policy differs from what you await...
>
What make you believe I won't be happy with
> The id of data items is the only way to refer to data items on the
> protocol side. So I need a *weak association* between an id and the data
> item (if any) of that id. I do not want to keep (in some ordinary Go map,
> for example) the association between ids and their data items