consider breaking into multiple crates
Since the core APIs of things like Printer
, Runtime
, and so forth are likely to stabilize much faster than the APIs of View
trait implementors, it may be beneficial to break into multiple crates. There are two schemes I can think of:
-
glyph_ui
andglyph_ui_views
-
glyph_ui
would act as the core crate and the latter would contain the contents of the currentglyph_ui::view
module - Users would then be expected to depend on both crates, assuming they want to use the views provided by this project
-
-
glyph_ui
,glyph_ui_core
, andglyph_ui_views
-
glyph_ui_core
would serve the same purpose asglyph_ui
would in the previous section, andglyph_ui
would be repurposed as a crate that depends on both thecore
andviews
crates and re-exports both of their items - Users could then simply depend solely on the
glyph_ui
crate instead of having to manage two separate dependencies
-