Beoran

@ianlancetaylor If this proposal makes it harder for ports to be available then this will damage the community. Maybe I am staying the obvious, but would it be possible for...

@ianlancetaylor With regards to this proposal: 1. Seeing the current difficulty in maintaining a secondary port. I think the main Go project should provide as many resources as possible. 2....

@paulzhol Thanks for providing concrete pain points and suggestions. I think it is important they are brought up here. @ianlancetaylor It kind of worries me that Google does not seem...

@ianlancetaylor I understand that the point if this proposal is to make the process match reality. It's just that I don't like the current reality, so I am arguing we...

I think this move to make kernels callable only though a blessed C library is a bad idea, in particular for all users of programming languages that are not C-like....

Here, I agree with @iceiceleo that OpenBSD (as wel as Solaris, Windows, etc) are in the wrong. A kernel should have a stable programming language-neutral direct syscall interface. It's unfortunate...

@geseq While value based semantics can indeed improve performance, this drastically changes the API of Tengo. It would need to be versioned as v3 to make this change.

@geseq In that case, it might be an idea to try to implement full value semantics for all types for v3, not just for integrets. This might seem strange for...

Well, my main interest here is consistency. Now Tengo uses pointer semantics for v2 everywhere and that is easy to remember. Having a mix of pointer and value semantics is...

Fair enough to use pointer semantics for arrays and maps, but in Go strings also have value semantics. I wonder if that would also work in Tengo?