Hi Joachim,
Thank you for the advice.
I'll try to correspond as follows:
* To use Travis for simple build check
* To use Phab or (slow) local machine for validation
* To use Phab for review
* To use Github PR for getting advice and confirm
I'll enjoy it carefully:)
Regards,
Takenobu
Hi,
ghc has an exception in place from travis; I fear it does not carry
over to forks.
If you have commit rights to GHC, you can develop in a branch.
Maybe a pull request works as well, not sure whether that uses the time
limit of the official repo or yours. Worth a try! Just write tin the PR
Hi Edward, devs,
Thank you for kind explanation.
I understood the situation.
Is it common to use paid plans when building GHC [1]?
[1]: https://travis-ci.org/ghc/ghc
Regards,
Takenobu
2017-02-04 10:41 GMT+09:00 Edward Z. Yang :
> Even with a paid plan, you only have 120 min
Even with a paid plan, you only have 120 min to run your build.
That might be enough in your case but in Cabal's Travis project
I've started playing tricks where I upload the build products
somewhere, and then redownload them in a new job before running tests.
Edward
Excerpts from Takenobu
| Typeable1.hs:22:5: error:
| • Couldn't match kind ‘* -> (* -> *) -> (* -> *) -> * -> *’
| with ‘forall k. (* -> *) -> (k -> *) -> k -> *’
I still don't see why we end up equating a polykind with a kind.
| Anyways, hopefully this will be resolved with the
Here [1] is the tweak we do in HaRe to get the right dynflags
Alan
[1]
https://github.com/alanz/HaRe/blob/master/src/Language/Haskell/Refact/Utils/Utils.hs#L224
On 3 Feb 2017 5:59 p.m., "Matthew Pickering"
wrote:
> You are right. I looked more closely now and it
Ben Gamari writes:
> Simon Peyton Jones writes:
>
>> Meanwhile to get you rolling, you can replace rewritableTyVars with
>> tyCoVarsOfType and it'll all work, just a bit less efficiently.
>>
> Thanks Simon! Indeed that allows things to proceed and
You are right. I looked more closely now and it looks like
"parseModule" and so on overwrite the DynFlags with a cached version
before running the relevant piece of the pipeline.
857hsc_env <- getSession
858let hsc_env_tmp = hsc_env { hsc_dflags = ms_hspp_opts ms }
859hpm <- liftIO
On Fri, Feb 03, 2017 at 12:21:38PM +, Christopher Done wrote:
> I tried the following before calling getModInfo, expecting there to be
> no output anymore:
>
> + GHC.setSessionDynFlags
> +df {log_action = \ref dflags severity srcSpan style msg -> return ()}
That is pretty much
Adding `handleSourceError` around it makes no difference.
Which makes sense, as I don't think warnings count as exceptions,
otherwise my code would never have completed in the first place.
On 3 February 2017 at 12:50, Matthew Pickering
wrote:
> The errors are
Simon Peyton Jones writes:
> Ben, Richard
>
> rewritableTyVarsOfType is used when deciding whether to split a [WD]
> constraint into [W] and [D]. For example, if we are adding
>[WD] C a
> and there is an inert
>[WD] a ~ Int
> then we want to split the [WD] into
>
The errors are eventually caught and printed by "handleSourceError"
which is used a few times in your code. You could either modify one of
these to not print out any errors or try something more intelligent
like is in `parUpsweep_one` which does use the `log_action` in order
to print the errors
In Intero, after loading modules, for each one I run the following
function:
https://github.com/commercialhaskell/intero/blob/300ac5a/src/GhciInfo.hs#L75..L85
If there are warnings or any output, they get outputted. As they are
already outputted by regular :load, I don’t need the same output
13 matches
Mail list logo