You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks cool! In the 'echo' example, it looked like the Go values were treated as opaque in your Idris code. Would it be possible to inspect internal values in composite Go types like structs, maps etc. from Idris?
The text was updated successfully, but these errors were encountered:
Thanks for your interest in idris-go! There is no real reason why the Go values couldn't be less opaque, except of course that someone has to implement it :-)
The much bigger topic I see right now is that everything is represented as unsafe pointer. So most time when running a program is spent chasing pointers and doing garbage collection. That makes idris-go a bit unattractive in practice, I'm afraid. On the other hand I don't see why a smarter representation/translation shouldn't be possible.
Looks cool! In the 'echo' example, it looked like the Go values were treated as opaque in your Idris code. Would it be possible to inspect internal values in composite Go types like structs, maps etc. from Idris?
The text was updated successfully, but these errors were encountered: