hobofan
commented
8 years ago @mitchmindtree : I mean in the end you don't have to use use collenchyma::*;, but I think it is important that all important parts are exported from the root module, so you don't have to know how Collenchyma is structured internally (which also allows us more freedom in refactoring).
It's also just a first step, I just put in what I knew from experience you would usually need to use Collenchyma, but there might be a one or two that aren't really needed. So on one side we might clean that up a bit more once we start approaching a 1.0 state, on the other hand I would also like to add another module, which exports everything that is important for plugin developers (this was focused on plugin-users).
homu
Just thought I'd mention that personally I'm not a fan of the glob imports, mainly for reasons you've probably already heard before :smile_cat:
Although it saves a step for the writer, it puts an extra step in the process of determining where names are being imported from, which imported names are actually being used and what traits might different methods be coming from. Normally I like to opt for moving as much of the burden from the reader to the writer as possible, but everyone has their own opinion here so feel free to disregard this comment!