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
I can access sdl::sys but not sdl::mixer::sys from my own code. This seems useful as I am trying to access functions not exposed by the sdl2 bindings.
In the base sdl library it is defined as pub extern crate sdl2_sys as sys;. In the mixer module it is declared as use sys;. It feels like this is a simple oversight that is a non-controversial change.
I am still early days learning Rust. I may likely be doing something incorrect, or requesting something inappropriate.
The text was updated successfully, but these errors were encountered:
No you are totally right, it should be fixed. sdl2_mixer was another crate at first (and was merged into this one later on), but at that time its ::sys was not public, and making the sys public was not part of the initial merge plan. This is related to issue #647, which has for roots closed issue #564.
I can access
sdl::sys
but notsdl::mixer::sys
from my own code. This seems useful as I am trying to access functions not exposed by the sdl2 bindings.In the base sdl library it is defined as
pub extern crate sdl2_sys as sys;
. In the mixer module it is declared asuse sys;
. It feels like this is a simple oversight that is a non-controversial change.I am still early days learning Rust. I may likely be doing something incorrect, or requesting something inappropriate.
The text was updated successfully, but these errors were encountered: