So, the fastest way on the compile-side for making collections of functions 
(optionally, tied to some common data type) is using closures? I thought so 
also, that's the direction I went instead of interfaces in my own work for 
the same reason.

On Sunday, 29 April 2018 16:52:44 UTC+3, Max wrote:
>
> About the "other languages extensions":
>
> it's obviously easier than modifying the official Go compiler, but it's 
> usually still a major task,
> especially if it involves modifying the "poor man's compiler" fast.Comp
> which converts a parsed ast.Node into a tree of function closures for 
> execution.
>
> If you have a specific example in mind and you describe it, I can be more 
> specific.
>
> On Saturday, April 28, 2018 at 11:59:41 PM UTC+2, Maxim Khitrov wrote:
>>
>> Do you have examples of adding custom ":xyz" or other language 
>> extensions? 
>>
>

-- 
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.

Reply via email to