The gui-lib might be an example. It provides modules spanning
different collections such as racket/gui, framework/ and mrlib/.

https://github.com/racket/gui/tree/master/gui-lib

On Wed, Aug 29, 2018 at 7:13 AM, Erich Rast <er...@snafu.de> wrote:
> On Wed, 29 Aug 2018 06:46:49 -0500
> Philip McGrath <phi...@philipmcgrath.com> wrote:
>
>
>> You don't need a multi-collection package to do this. If your
>> structure is:
>>
>> appy/
>> |
>> |--info.rkt
>> |--main.rkt
>> |--gui.rkt
>> |--…
>>
>> Then `(require appy)` will import "main.rkt" and `(require appy/gui)`
>> will import "gui.rkt".
>
> Oh, that's very useful info I didn't know that. I thought this
> possibility is exactly the purpose of multi-collection packages. I'll
> make it flat again ASAP.
>
> Out of curiosity, if it's not the above selective importing, what *is*
> the main use case for multi-collection packages?
>
> Best,
>
> Erich
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to racket-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to