Brandon Moore schrieb:
>> From: max ulidtko
>> ...
> 3) There's also package-qualified imports, but I don't think you should use
> them -
> if there are actually conflicts on those top-level module names, the package
> should be fixed sooner rather than later.
4) Write wrapper modules with Hie
- Original Message -
> From: max ulidtko
> To: haskell-cafe@haskell.org
> Cc:
> Sent: Monday, May 23, 2011 11:38 PM
> Subject: [Haskell-cafe] Cabal: wrapping namespace of a package into top-level
> module
>
> Hi haskell-cafe.
>
> I have a package which
On Tue, May 24, 2011 at 00:38, max ulidtko wrote:
> I have a package which builds with cabal pretty fine, but there is
> namespace issue which disturbs me. The problem is that the package
> exports (to the toplevel namespace!) some modules with fairly general
> names, like Tests, Basics, Applicat
On 24 May 2011 14:38, max ulidtko wrote:
> Hi haskell-cafe.
>
> I have a package which builds with cabal pretty fine, but there is
> namespace issue which disturbs me. The problem is that the package
> exports (to the toplevel namespace!) some modules with fairly general
> names, like Tests, Basic
Hi haskell-cafe.
I have a package which builds with cabal pretty fine, but there is
namespace issue which disturbs me. The problem is that the package
exports (to the toplevel namespace!) some modules with fairly general
names, like Tests, Basics, Applications. This is probably an oversight
of the
