<div dir="ltr"><div><div>That's not what I'm observering. I intentially put -Wall and some odd code in a local copy of pipes-csv, stack clean, stack build.<br><br>/home/toad/working/pipes-csv-1.4.0/src/Pipes/Csv.hs:216:3: Warning:<br> A do-notation statement discarded a result of type ‘String’<br> Suppress this warning by saying ‘_ <- getLine’<br> or by using the flag -fno-warn-unused-do-bind<br><br></div>In another project, stack clean, stack build<br><br>pipes-csv-1.4.0: configure<br>pipes-csv-1.4.0: build<br>pipes-csv-1.4.0: copy/register<br><br></div>Nothing at all.<br><div><br></div><div>stack.yaml is basically this, but with a few extra packages.<br><br>flags: {}<br>packages:<br>- '.'<br>- '../pipes-csv-1.4.0'<br>extra-deps: []<br>resolver: lts-3.1<br><br></div><div>stack --version<br>Version 1.1.2 x86_64 hpack-0.14.0<br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 14, 2016 at 4:10 PM, Christopher Allen <span dir="ltr"><<a href="mailto:cma@bitemyapp.com" target="_blank">cma@bitemyapp.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I see what is meant now, but it's not really applicable. If I am<br>
co-developing a package and its dependencies, I add them as packages<br>
(not deps) to my stack.yaml and still get the warnings.<br>
<br>
Example:<br>
<br>
>From the stack.yaml for the package that uses my previous example's library:<br>
<br>
<br>
packages:<br>
- '.'<br>
- ../simple-library<br>
<br>
<br>
Then stack build'ing the project (uses-sl) that depends on<br>
simple-library which as a module with a warning:<br>
<br>
<br>
$ stack build<br>
simple-library-0.1.0.0: build<br>
Progress: 1/2<br>
-- While building package simple-library-0.1.0.0 using:<br>
/home/callen/.stack/setup-exe-<wbr>cache/x86_64-linux/setup-<wbr>Simple-Cabal-1.24.0.0-ghc-8.0.<wbr>1<br>
--builddir=.stack-work/dist/<wbr>x86_64-linux/Cabal-1.24.0.0 build<br>
lib:simple-library exe:simple-library-exe --ghc-options " -ddump-hi<br>
-ddump-to-file"<br>
Process exited with code: ExitFailure 1<br>
Logs have been written to:<br>
/home/callen/work/uses-sl/.<wbr>stack-work/logs/simple-<wbr>library-0.1.0.0.log<br>
<br>
Preprocessing library simple-library-0.1.0.0...<br>
[1 of 1] Compiling SimpleLib ( src/SimpleLib.hs,<br>
.stack-work/dist/x86_64-linux/<wbr>Cabal-1.24.0.0/build/<wbr>SimpleLib.o )<br>
<br>
/home/callen/work/simple-<wbr>library/src/SimpleLib.hs:7:3: warning:<br>
<span class="">[-Wunused-do-bind]<br>
A do-notation statement discarded a result of type ‘[Char]’<br>
</span> Suppress this warning by saying ‘_ <- return "hello"’<br>
<br>
<br>
<br>
One of the first things I did when figuring out Stack was to look at<br>
how Yesod used it:<br>
<a href="https://github.com/yesodweb/yesod/blob/master/stack.yaml" rel="noreferrer" target="_blank">https://github.com/yesodweb/<wbr>yesod/blob/master/stack.yaml</a><br>
<div class="HOEnZb"><div class="h5"><br>
On Wed, Sep 14, 2016 at 2:56 PM, David McBride <<a href="mailto:toad3k@gmail.com">toad3k@gmail.com</a>> wrote:<br>
> The rule of thumb seems to be, if you do a stack build and it decides to<br>
> build multiple packages, it hides this log info.<br>
><br>
> I understand why it does that, I should be able to build lens without<br>
> worrying about tons of spurious output, but at the same time it is common<br>
> for me to have an entire tree of packages I'm developing and it often<br>
> obscures errors that are happening in my own packages. At the very least,<br>
> if it is only building local packages, I'd very much like to see that<br>
> output.<br>
><br>
> On Wed, Sep 14, 2016 at 3:42 PM, Patrick Pelletier<br>
> <<a href="mailto:code@funwithsoftware.org">code@funwithsoftware.org</a>> wrote:<br>
>><br>
>> On 9/14/16 12:21 PM, Christopher Allen wrote:<br>
>>><br>
>>> What are you talking about?<br>
>>><br>
>>> $ stack build<br>
>>> simple-library-0.1.0.0: unregistering (local file changes: src/Lib.hs)<br>
>>> simple-library-0.1.0.0: build<br>
>>> Preprocessing library simple-library-0.1.0.0...<br>
>>> [1 of 1] Compiling Lib ( src/Lib.hs,<br>
>>> .stack-work/dist/x86_64-linux/<wbr>Cabal-1.24.0.0/build/Lib.o )<br>
>>><br>
>>> /home/callen/work/simple-<wbr>library/src/Lib.hs:7:3: warning:<br>
>>> [-Wunused-do-bind]<br>
>>> A do-notation statement discarded a result of type ‘[Char]’<br>
>>> Suppress this warning by saying ‘_ <- return "woot"’<br>
>>> Preprocessing executable 'simple-library-exe' for<br>
>>> simple-library-0.1.0.0...<br>
>><br>
>><br>
>> Weird. That's not how it works for me:<br>
>><br>
>> whiteandnerdy:normalize ppelleti$ stack build<br>
>> normalization-insensitive-2.0: unregistering (local file changes:<br>
>> Data/Unicode/<wbr>NormalizationInsensitive.hs<br>
>> Data/Unicode/<wbr>NormalizationInsensitive/<wbr>Internal.hs)<br>
>> normalization-insensitive-2.0: configure<br>
>> normalization-insensitive-2.0: build<br>
>> normalization-insensitive-2.0: copy/register<br>
>> photos-0.1.0.0: configure<br>
>> photos-0.1.0.0: build<br>
>> photos-0.1.0.0: copy/register<br>
>> Completed 2 action(s).<br>
>> whiteandnerdy:normalize ppelleti$ cat<br>
>> .stack-work/logs/<wbr>normalization-insensitive-2.0.<wbr>log<br>
>> Configuring normalization-insensitive-2.0.<wbr>..<br>
>> Preprocessing library normalization-insensitive-2.0.<wbr>..<br>
>> [1 of 3] Compiling Data.Unicode.<wbr>NormalizationInsensitive.<wbr>Internal (<br>
>> Data/Unicode/<wbr>NormalizationInsensitive/<wbr>Internal.hs,<br>
>> .stack-work/dist/x86_64-osx/<wbr>Cabal-1.22.5.0/build/Data/<wbr>Unicode/<wbr>NormalizationInsensitive/<wbr>Internal.o<br>
>> )<br>
>><br>
>> Data/Unicode/<wbr>NormalizationInsensitive/<wbr>Internal.hs:30:1: Warning:<br>
>> The import of ‘Data.Bool’ is redundant<br>
>> except perhaps to import instances from ‘Data.Bool’<br>
>> To import instances alone, use: import Data.Bool()<br>
>><br>
>> Data/Unicode/<wbr>NormalizationInsensitive/<wbr>Internal.hs:38:1: Warning:<br>
>> The import of ‘otherwise, &&, <=, +’<br>
>> from module ‘Prelude’ is redundant<br>
>><br>
>> Data/Unicode/<wbr>NormalizationInsensitive/<wbr>Internal.hs:57:1: Warning:<br>
>> Module ‘Data.ByteString.UTF8.<wbr>Normalize’ is deprecated:<br>
>> Convert ByteString to Text and then normalize<br>
>><br>
>> Data/Unicode/<wbr>NormalizationInsensitive/<wbr>Internal.hs:135:1: Warning:<br>
>> Top-level binding with no type signature: mode :: NormalizationMode<br>
>><br>
>> Data/Unicode/<wbr>NormalizationInsensitive/<wbr>Internal.hs:143:17: Warning:<br>
>> In the use of ‘B.normalize’<br>
>> (imported from Data.ByteString.UTF8.<wbr>Normalize):<br>
>> Deprecated: "Convert ByteString to Text and then normalize"<br>
>><br>
>> Data/Unicode/<wbr>NormalizationInsensitive/<wbr>Internal.hs:147:33: Warning:<br>
>> In the use of ‘B.normalize’<br>
>> (imported from Data.ByteString.UTF8.<wbr>Normalize):<br>
>> Deprecated: "Convert ByteString to Text and then normalize"<br>
>> [2 of 3] Compiling Data.Unicode.<wbr>NormalizationInsensitive.<wbr>Unsafe (<br>
>> Data/Unicode/<wbr>NormalizationInsensitive/<wbr>Unsafe.hs,<br>
>> .stack-work/dist/x86_64-osx/<wbr>Cabal-1.22.5.0/build/Data/<wbr>Unicode/<wbr>NormalizationInsensitive/<wbr>Unsafe.o<br>
>> )<br>
>> [3 of 3] Compiling Data.Unicode.<wbr>NormalizationInsensitive (<br>
>> Data/Unicode/<wbr>NormalizationInsensitive.hs,<br>
>> .stack-work/dist/x86_64-osx/<wbr>Cabal-1.22.5.0/build/Data/<wbr>Unicode/<wbr>NormalizationInsensitive.o<br>
>> )<br>
>><br>
>> Data/Unicode/<wbr>NormalizationInsensitive.hs:<wbr>25:31: Warning:<br>
>> ‘normalize’ is exported by ‘Normalizable(normalize)’ and ‘normalize’<br>
>> In-place registering normalization-insensitive-2.0.<wbr>..<br>
>> Installing library in<br>
>><br>
>> /Users/ppelleti/programming/<wbr>haskell/normalize/.stack-work/<wbr>install/x86_64-osx/lts-6.1/7.<wbr>10.3/lib/x86_64-osx-ghc-7.10.<wbr>3/normalization-insensitive-2.<wbr>0-KLVtcrPtbow6nG8kRB6WPM<br>
>> Registering normalization-insensitive-2.0.<wbr>..<br>
>> whiteandnerdy:normalize ppelleti$<br>
>><br>
>> I hadn't even been aware of these warnings in the package I was<br>
>> developing, until Harendra Kumar pointed them out to me, after I had<br>
>> uploaded a candidate to Hackage.<br>
>><br>
>> --Patrick<br>
>><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> Haskell-Cafe mailing list<br>
>> To (un)subscribe, modify options or view archives go to:<br>
>> <a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe" rel="noreferrer" target="_blank">http://mail.haskell.org/cgi-<wbr>bin/mailman/listinfo/haskell-<wbr>cafe</a><br>
>> Only members subscribed via the mailman list are allowed to post.<br>
><br>
><br>
<br>
<br>
<br>
</div></div><div class="HOEnZb"><div class="h5">--<br>
Chris Allen<br>
Currently working on <a href="http://haskellbook.com" rel="noreferrer" target="_blank">http://haskellbook.com</a><br>
</div></div></blockquote></div><br></div>