I assume you know where your interface{} will no longer be used. Why not
put in an explicit optimization structure delete there? There's already a
New, make a Done or something like that.
Matt
On Sunday, January 21, 2018 at 6:41:00 PM UTC-6, simon place wrote:
>
> after a bit of thought, its not ideal.
>
> it would work, but defeats part of the objective, which was for the
> optimisations to be transparent, having the defer, or callbacks, in the
> calling function breaks the isolation.
>
> i could insert callbacks in the base code which would just be redundant
> when used with an unoptimised routine. i'll see if there is a significant
> penalty for that, it would be ironic if just making these global
> optimisations possible results in code, not using any, being slower.
>
>
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
