You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create a new project with stack new blah simple. Then unpack any odd package from Hackage with compiler warnings into vendor/foo, and make your project depend on it:
Now compile everything with stack build --pedantic. The build will fail due to a compiler warning in foo. I would argue that since foo is a vendor package that the programmer has little control over, --pedantic shouldn't apply to any package marked with extra-dep: true.
The text was updated successfully, but these errors were encountered:
Create a new project with
stack new blah simple
. Then unpack any odd package from Hackage with compiler warnings intovendor/foo
, and make your project depend on it:Now compile everything with
stack build --pedantic
. The build will fail due to a compiler warning infoo
. I would argue that sincefoo
is a vendor package that the programmer has little control over,--pedantic
shouldn't apply to any package marked withextra-dep: true
.The text was updated successfully, but these errors were encountered: