GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
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
Part of gtk-rs/gir#295
Waiting for appveyor to finish and then I merge.
Don't forget gtk's PR ;)
Ah damn, you're right!
While all these functions are in auto/functions.rs, I don't see them re-exported from lib.rs anywhere
It can be used by long name
But previously it was available as e.g. utils::get_application_name(). Now it would be auto::functions::get_application_name() (and the auto module is not pub-re-exported so that won't work)
edit: actually it is pub-re-exported. But nonetheless, this would be an API change that does not seem needed, and also doesn't seem ideal from a user-experience point of view :)
Hm, you right. I missed fact that auto non public in all crates :(
What better do: add to lib.rs pub mod functions with reexports or something else?
@GuillaumeGomez maybe you have better idea?
pub mod functions
Or just make auto public?
We never target a specific date. When we judge we have enough changes or someone really want/need a release to publish his/her crate, we do it.
Makes sense :) before a big release, it might be a good idea to do a small release with the floating reference bugfix, just of glib.
There is no such things as a small release (because it takes a lot of time to make one).
It's not possible to just "cargo publish" glib with a new version number and that patch, and keep everything else the same?
Hum, might be actually.
Generate global functions
This is last for reexport