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
The current method of generation leaves a lot of implementation types and functions around, such as Wrapper functions, while also bloating files up. Too many files and #includes also drag the compile time out, so it's not ideal.
A better approach to this would be to make girgen create a sys package inside pkg/internal/sys, which would contain implementation classes like a type GtkWidget struct as well as the wrapper function. This would not only clear up the documentation, it would also speed up compiling by having everything in one large file. Types could also embed other structs instead of having to embed the public interface, which would reduce class types' sizes to just 8 bytes.
The text was updated successfully, but these errors were encountered:
After attempts in implementing this, a package sys is not feasible, because functions and constructors defined in the main package may have to import the sys package for types, while the sys package is definitely importing the main package for its type signatures.
The current method of generation leaves a lot of implementation types and functions around, such as Wrapper functions, while also bloating files up. Too many files and
#include
s also drag the compile time out, so it's not ideal.A better approach to this would be to make
girgen
create asys
package insidepkg/internal/sys
, which would contain implementation classes like atype GtkWidget struct
as well as the wrapper function. This would not only clear up the documentation, it would also speed up compiling by having everything in one large file. Types could also embed other structs instead of having to embed the public interface, which would reduce class types' sizes to just 8 bytes.The text was updated successfully, but these errors were encountered: