-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider shortening the output #95
Comments
Related with #32 The generated code is longer and more explicit by design to avoid having to keep track of whether declarations in the generated code shadows a declaration being imported. |
It seems that you have already covered this issue. I hoped the |
I think that it is a good idea. |
Okay, let's keep it open, but I think we should give it pretty low priority for now since there are a lot of more important things to address. |
I found another thing that might help. When functions are generated they are given parameter names as |
I agree, I also do not like |
Currently in hand generated code there are tricks to make the code shorter and cleaner such as use of imports. A good example is the following:
https://github.com/scala-native/scala-native/blob/master/nativelib/src/main/scala/scala/scalanative/posix/dirent.scala
The keys points are the imports that eliminate the
native.
andNat.
prefixes. Also, in hand generated code thestruct
is just nameddirent
.The text was updated successfully, but these errors were encountered: